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

Re: Merge commit subjects git.git

From
Thomas Rast <trast@student.ethz.ch>
Date
Jul 18, 2010, 15:33 UTC
Message-ID
<201007181733.59704.trast@student.ethz.ch>
In-Reply-To
<AANLkTikavL0DH8FgFxBw7hbGLtj2tqxnP-BT77zo5FJT@mail.gmail.com>
Jay Soffian wrote:
Show 11 quoted lines
> Color me curious, but why do the merge commit message in git.git
> sometimes look like this:
> 
>   Merge branch 'jn/paginate-fix'
> 
> And other times like this:
> 
>   Merge remote branch 'ko/master' into jc/read-tree-cache-tree-fix
> 
> I don't really see any rhyme or reason about when the "into ..." is
> there and when it's not.

A merge that does not have the 'into <branch>' bit is a merge to master:

static void do_fmt_merge_msg_title(struct strbuf *out,
	const char *current_branch) {
[...]
	if (!strcmp("master", current_branch))
		strbuf_addch(out, '\n');
	else
		strbuf_addf(out, " into %s\n", current_branch);
}
-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Jay SoffianNext: Ævar Arnfjörð Bjarmason
Message 2 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.