From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
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>,
Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Merge commit subjects git.git
Date: Mon, 19 Jul 2010 16:10:57 +0200 [thread overview]
Message-ID: <20100719141057.GA13051@vidovic> (raw)
In-Reply-To: <AANLkTinTOMxWVM9kwhIfcG44SqOjpexY-Xy6kZYkemU9@mail.gmail.com>
The 18/07/10, Sverre Rabbelier wrote:
> 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?
To talk about pros and cons I wonder what would be the benefits of
changing this. I guess most projects probably best keeping the history
consistent for all the merge commit messages.
I think this is more sensible than giving the same behaviour /across/
different repositories (for only which not following the "master"
convention).
--
Nicolas Sebrecht
next prev parent reply other threads:[~2010-07-19 14:11 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
2010-07-18 18:03 ` Ilari Liusvaara
2010-07-19 14:10 ` Nicolas Sebrecht [this message]
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=20100719141057.GA13051@vidovic \
--to=nicolas.s.dev@gmx.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.