[Pkg-octave-devel] Updating the packages on RC-unrelated issues

[Rafael Laboissiere]

* Mike Miller <mtmiller at ieee.org> [2012-07-14 11:50]:

> On Sat, Jul 14, 2012 at 2:48 AM, Rafael Laboissiere
> <rafael at laboissiere.net> wrote:
> > Ok, I just fixed Bug#681065 and, in the process, created the experimental
> > branch in the Git repository for the octave package.
> >
> > Using "gbp-clone --all" will create a local branch "experimental" which
> > is set up to track "origin/experimental".
> 
> I didn't know about --all, very useful!
> 
> > Otherwise, after git pull, I
> > guess that the following commands will be enough:
> >
> >     git branch experimental origin/experimental
> >     git checkout experimental
> 
> Or "git checkout -b experimental origin/experimental".
> 
> I've had to go "experimental" in one of my other packages, I checked
> in a debian/gbp.conf on the experimental branch like so:
> 
> [DEFAULT]
> pristine-tar = True
> debian-branch = experimental
> 
> to avoid needing to do "--git-debian-branch=experimental" on every
> git-buildpackage.  Of course I'll have to remember to change it back
> or delete it when merging back into master.

Thanks for the tips!
 
Rafael