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

Ugly merge messages

From
Linus Torvalds <torvalds@osdl.org>
Date
Sep 19, 2005, 00:05 UTC
Message-ID
<Pine.LNX.4.58.0509181649390.9106@g5.osdl.org>
Junio,
 your merge messages are pretty ugly.

You often merge from a local branch in the current tree, which is fine, but it generates a message like

	Octopus merge of the following:
	refs/heads/pu from .
	branch 'nuker' of .
	branch 'merge' of .

which just looks wrong. At least to me, the dot looks more like a end-of-incomplete-sentence than a source of data.

Also, the "first" branch is really special, since that's the branch you're merging _into_.

Wouldn't it look a lot nicer if this read as
	Octopus merge of the following:
	branch 'nuker'
	branch 'merge'
	into branch 'pu'
or something?

But that still has the problem that the single-line description (ie gitk, shortlog etc) is totally useless. So maybe we shouldn't care about the destination branch (we don't do that for normal merges), and just aim for something like

	Octopus merge of branches 'nuker', 'merge'
instead?

Hmm? At least for the kernel, the shortlog really is pretty important, because the full log is often so big that it's easy to miss things in it.

		Linus
Next: Junio C Hamano
Message 1 of 2 in “Ugly merge messages”
  1. Linus TorvaldsSep 19, 2005
  2. Junio C HamanoSep 19, 2005

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.