Re: Git Feature Branch Naming Policy

2011-04-26 Thread Alexander Neundorf
On Tuesday 26 April 2011, John Layt wrote: > Hi, > > Did anything come out from discussions on feature branch naming in git? > With GSoC starting soon we'll be getting a lot of new feature branches and > it would be nice if they were consistantly named to make them easy to find > and manage. > > S

Re: Git Feature Branch Naming Policy

2011-04-26 Thread John Layt
On Tuesday 26 Apr 2011 17:37:47 Torgny Nyblom wrote: > Why this long name with multiple namespaces, the branches should be deleted > once merged so we won't have a collection of old soc branches around for > long? > > /Regards > Torgny Well it's based on the original naming proposal to try keep t

Re: Git Feature Branch Naming Policy

2011-04-26 Thread Shaun Reich
>> I'd prefer to see the gsoc branches under a common prefix in the main >> project repo rather than as personal branches or repos: I think that's a good idea too, especially given (below). >> >>   origin/gsoc2011// Probably don't need subproject, since the branch name will probably/should tell

Re: Git Feature Branch Naming Policy

2011-04-26 Thread John Layt
On Tuesday 26 Apr 2011 16:18:22 Harald Sitter wrote: > On Tuesday 26 April 2011 15:52:18 John Layt wrote: > > I'd prefer to see the gsoc branches under a common prefix in the main > > > > project repo rather than as personal branches or repos: > > origin/gsoc2011// > > > > e.g. in kdelibs.git h

Re: Git Feature Branch Naming Policy

2011-04-26 Thread Torgny Nyblom
On Tuesday 26 April 2011 15.52.18 John Layt wrote: > Hi, > > Did anything come out from discussions on feature branch naming in git? > With GSoC starting soon we'll be getting a lot of new feature branches and > it would be nice if they were consistantly named to make them easy to find > and mana

Re: Git Feature Branch Naming Policy

2011-04-26 Thread Harald Sitter
On Tuesday 26 April 2011 15:52:18 John Layt wrote: > I'd prefer to see the gsoc branches under a common prefix in the main > project repo rather than as personal branches or repos: > > origin/gsoc2011// > > e.g. in kdelibs.git have "origin/gsoc2011/kdecore/astronomical-calendars" What if a stu

Git Feature Branch Naming Policy

2011-04-26 Thread John Layt
Hi, Did anything come out from discussions on feature branch naming in git? With GSoC starting soon we'll be getting a lot of new feature branches and it would be nice if they were consistantly named to make them easy to find and manage. See http://community.kde.org/20110213_GitWorkflowAgenda