Re: Merge commit subjects git.git

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Jul 18, 2010, 17:22 UTC
Message-ID: <AANLkTim4FxPdHsDxkRmHzJT24LnZyiv9xLUqbTUndS9T@mail.gmail.com>
In-Reply-To: <AANLkTinTOMxWVM9kwhIfcG44SqOjpexY-Xy6kZYkemU9@mail.gmail.com>

On Sun, Jul 18, 2010 at 16:56, Sverre Rabbelier <srabbelier@gmail.com> wrote:

Show 8 quoted lines

> Heya,
>
> On Sun, Jul 18, 2010 at 10:33, Thomas Rast <trast@student.ethz.ch> wrote:
>>        if (!strcmp("master", current_branch))
>
> Wow, I thought the only place where we gave "master" any special
> meaning was in that we create it as the default branch. Can't we fix
> this to be less hard-coded?

In addition, Ilari on IRC pointed this out:

    < avar> What does git use to determine what branch gets checked out
            (not always master) on git clone URL?
    < Ilari> avar: HEAD
    < avar> Ah, just the HEAD of the remote, but that doesn't help after
            you've switched branches locally to find out what the main
            is..
    < Ilari> avar: Except that if you have another branch with same commit
             as the one you set to default, either of them may be selected
             (if one is 'master', then the tie is broken for it).

I.e. master is also treated more magically than others when cloning. But I couldn't find the code that does this, so perhaps it doesn't do that.