[Pkg-javascript-devel] libv8 upstream branches and git-buildpackage

Jérémy Lal kapouer at melix.org
Sat Feb 12 15:44:54 UTC 2011


On 12/02/2011 11:57, Jonas Smedegaard wrote:
> On Sat, Feb 12, 2011 at 11:06:23AM +0100, Jérémy Lal wrote:
>> gbp layout in collab-maint/libv8
>> --------------------------------
>>
>> * master, upstream
>>  current work on latest upstream libv8, meant to be uploaded to  /experimental/
>> * 2.2/master, 2.2/upstream
>>  that's libv8 in squeeze
>> * 2.5/master, 2.5/upstream
>>  and in testing/unstable
>>
>> I added debian/gbp.conf in each debian branch to make sure git-buildpackage is happy.
> 
> I would prefer to name packaging branches after the Debian suites rather that upstream branches, and also to prefix with the main default gbp branch names to ease tab-completion.
> 
> Therefore I recommend to change to the following layout:
> 
> * pristine-tar
>   single branch used for all pristine-tar imports
> * master, upstream
>   head of "main" packaging development, i.e. for Debian unstable
> * master-experimental, upstream-experimental
>   head of "experimental" packaging, i.e. for Debian experimental
> 
> This way we can reuse branches instead of leaving behind an (irrelevant, IMO) trail of branches behind for each upstream branch that we choose to work on.

Done and pushed, with the addition of master-stable and upstream-stable branches.
So currently we have 2.5 in master, 3.0 in master-experimental, and 2.2 in master-stable.

Jérémy.




More information about the Pkg-javascript-devel mailing list