Git development branches

[Benjamin Port]

2011/1/6 Aleix Pol <aleixpol at kde.org>:
> 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).
> On the other hand, it's still a valid way to do so, so i'm fine with using
> it.
> Aleix
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>
Yes but to add remote, we need to know remote before, so we can list
branch before adding it...
Benjamin