From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Thomas Rast <trast@student.ethz.ch>,
Jay Soffian <jaysoffian@gmail.com>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: Merge commit subjects git.git
Date: Sun, 18 Jul 2010 17:22:01 +0000 [thread overview]
Message-ID: <AANLkTim4FxPdHsDxkRmHzJT24LnZyiv9xLUqbTUndS9T@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinTOMxWVM9kwhIfcG44SqOjpexY-Xy6kZYkemU9@mail.gmail.com>
On Sun, Jul 18, 2010 at 16:56, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> 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.
next prev parent reply other threads:[~2010-07-18 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-18 8:22 Merge commit subjects git.git Jay Soffian
2010-07-18 15:33 ` Thomas Rast
2010-07-18 16:18 ` Ævar Arnfjörð Bjarmason
2010-07-18 16:56 ` Sverre Rabbelier
2010-07-18 17:22 ` Ævar Arnfjörð Bjarmason [this message]
2010-07-18 18:03 ` Ilari Liusvaara
2010-07-19 14:10 ` Nicolas Sebrecht
2010-07-19 16:31 ` Junio C Hamano
2010-07-19 17:23 ` Jay Soffian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTim4FxPdHsDxkRmHzJT24LnZyiv9xLUqbTUndS9T@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=srabbelier@gmail.com \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).