[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: Git Feature Branch Naming Policy
From: John Layt <johnlayt () googlemail ! com>
Date: 2011-04-26 17:50:57
Message-ID: 201104261850.58096.johnlayt () googlemail ! com
[Download RAW message or body]
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/<subproject>/<branchname>
> >
> > e.g. in kdelibs.git have "origin/gsoc2011/kdecore/astronomical-calendars"
>
> What if a student wishes to have multiple branches (which are of interest
> to the mentor)?
>
> origin/gsoc2011/<subproject>/<gsocprojectname>/<gsocprojectbranch>
>
> comes to mind, which looks rather insanely long :S
Nah, they would just have it at the same level, I think we can cope with that.
Note in most projects/repos that <subproject> won't be needed, e.g. Marble
won't need it, it's only those monolithic repos with multiple apps or
libraries that you might need it to keep order.
John.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic