I could force-push upstream to track unstable, and put a gbp.conf or whatever in the experimental branch that makes sense, if you like. On Aug 21, 2014 12:32 PM, "Raphael Hertzog" <hert...@debian.org> wrote:
> Hi, > > On Thu, 21 Aug 2014, Luke Faraone wrote: > > This is an automated email from the git hooks/post-receive script. > > > > lfaraone pushed a change to branch master > > in repository python-django. > > > > from f8054c2 releasing package python-django version 1.6.5-5 > > new 3a30a56 Lets just release 1.6.6 from upstream instead. > > new 77afcf2 Revert "Release to unstable", wasn't actually > released. > > adds cc3322a Imported Upstream version 1.7~c1+20140722 > > adds f7bbf2d Imported Upstream version 1.7~c2 > > Hum, I should have imported Django 1.7 in another branch than "upstream" > because it makes for a weird history to have the branch go to 1.7 and then > come back to 1.6.6... > > We should pay some attention to those details when we manage multiple > branches. > > Cheers, > -- > Raphaël Hertzog ◈ Debian Developer > > Discover the Debian Administrator's Handbook: > → http://debian-handbook.info/get/ >
_______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
