Git development branches

[Benjamin Port]

Ok, so I go to create clones under my account, (if some people want to
look for our code, just see clones for bport)

Benjamin Port

2011/1/7 Aleix Pol <aleixpol at kde.org>:
> On Fri, Jan 7, 2011 at 10:50 AM, Andreas Pakulat <apaku at gmx.de> wrote:
>>
>> On 06.01.11 21:19:15, Aleix Pol wrote:
>> > On Thu, Jan 6, 2011 at 4:15 PM, Benjamin Port
>> > <port.benjamin at gmail.com>wrote:
>> >
>> > > Hello,
>> > > When we worked with gitorious we have our development branches under a
>> > > team repository.
>> > > Currently we can't do the same thing with git.kde.org
>> > > So there are two solutions (at least):
>> > > * Create branch under the main repository
>> > > * Create personnal clone
>> > >
>> > > For me it's more easy to create branch under the main repository:
>> > > *Easy to see quickly all development branch with a git branch -a
>> > > *Easy to switch from one branch to another branch
>> > > *Only one repository to clone
>> > > For this solution I suggest to:
>> > > *Create branch with a name convention like: somestuff-username (e.g.
>> > > qtdocumentation-bport), with this we can know on what a group work and
>> > > also know a "branch maintainer" to contact him.
>> > > *Remove branch when we have merged it in order to have a clean
>> > > repository all the time and not a large amount of branch.
>> > >
>> > > Regards,
>> > > Benjamin Port
>> > >
>> > > --
>> > > KDevelop-devel mailing list
>> > > KDevelop-devel at kdevelop.org
>> > > https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>> > >
>> >
>> >
>> > The only benefit is having the branch available to different developers
>> > because, according to #kde-sysadmin yesterday afternoon it's not
>> > possible to
>> > have team clones in git.kde.org. Other reasoning here is not important
>> > (as
>> > apaku said it's possible to list all branches just by adding the
>> > remote).
>>
>> Unlike what sysadmins say, the personal clones do have write access for
>> other developers. I've tested that on wednesday already with PovAddict
>> (sorry, dunno your realname :)) and you can also see that with ssh g.k.o
>> expand kdevelop
>>
>> Andreas
>>
>> --
>> You are number 6!  Who is number one?
>>
>> --
>> KDevelop-devel mailing list
>> KDevelop-devel at kdevelop.org
>> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
> In that case, I'd say it makes sense that in situations like ISI's the
> development is being held in personal clones since it's a very specific
> subset of people working on it.
> Aleix
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>