Re: git: using branches

[Simos Xenitellis <simos lists googlemail com>]

On Fri, Apr 17, 2009 at 8:55 PM, Luca Ferretti <elle uca libero it> wrote:
> 2009/4/17 Kalle Vahlman <kalle vahlman gmail com>:
>> 2009/4/17 Luca Ferretti <elle uca libero it>:
>>>
>>> I hope there is a more simple way to do this. This seems a nonsense to
>>> me: create a new local branch in order to commit+push on an existing
>>> branch on server...
>>
>> Uh, so assuming this comment is in reference to the way SVN works, how
>> did you commit to a branch without creating a local working copy in
>> SVN?
>
> Oh, no, my comment was in reference to the way MY MIND works ;)
>
> I mean, my mind expects something like those (fake) commands:
>  $ dcvs clone module
>  $ cd module
>  $ dvcs where-i-am
>  branch: master
>  $ dvcs switch revision-2-26
>  $ dvcs where-i-am
>  branch: revision-2-26
>
> In my mind a new local branch should be creaed only if you plan to
> work on a large feature, not just to "commit" a small change or
> existing patch.
>
> But of course this is my own vision of DVCS.

When you 'git checkout' another branch, you perform an offline process.
All the relevant information is already in the history, locally.
Regarding the issue of having to specify the 'local branch name',

I suppose  there must be some story behind the question 'Why do we specify
the branch name instead of reusing the remote branch name by default?
It feels somewhat weird.'.
With a big more experience we should be able to figure it out.

In any case, any issues that come up, albeit simple, should be discussed so
that we add it to the Git HowTo page on live.gnome.org,
http://live.gnome.org/TranslationProject/GitHowTo
Usability issues are very important too.

Simos