git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Merge commit subjects git.git

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Jul 19, 2010, 14:10 UTC
Message-ID
<20100719141057.GA13051@vidovic>
In-Reply-To
<AANLkTinTOMxWVM9kwhIfcG44SqOjpexY-Xy6kZYkemU9@mail.gmail.com>
The 18/07/10, Sverre Rabbelier wrote:
Show 6 quoted lines
> 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
Previous: Ilari LiusvaaraNext: Junio C Hamano
Message 7 of 9 in “Merge commit subjects git.git”
  1. Jay SoffianJul 18, 2010
  2. Thomas RastJul 18, 2010
  3. Ævar Arnfjörð BjarmasonJul 18, 2010
  4. Sverre RabbelierJul 18, 2010
  5. Ævar Arnfjörð BjarmasonJul 18, 2010
  6. Ilari LiusvaaraJul 18, 2010
  7. Nicolas SebrechtJul 19, 2010
  8. Junio C HamanoJul 19, 2010
  9. Jay SoffianJul 19, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.