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

Re: How to enhance merge commit message ?

From
ALAlexander Litvinov <litvinov2004@gmail.com>
Date
Jan 30, 2007, 05:23 UTC
Message-ID
<200701301123.59687.litvinov2004@gmail.com>
In-Reply-To
<7v8xfl6s27.fsf@assigned-by-dhcp.cox.net>
В сообщении от Tuesday 30 January 2007 10:45 Junio C Hamano написал(a):
> $ grep -A2 '^merge\.summary' Documentation/config.txt
> merge.summary::
> 	Whether to include summaries of merged commits in newly created
> 	merge commit messages. False by default.
Thanks !
Show 9 quoted lines
> This is a good option if you are doing the top-level "bundling
> of others' work -- people will base their further work on this"
> merges.  On the other hand, if you are merging from your uplevel
> because your work depends on something that was updated recently,
> having the merge summary is often pointless (because the merge
> would bring in many mostly unrelated commits, in addition to that
> something your work depends on).  I think Linus has explicitly
> asked this option not enabled by people he pulls from for this
> reason.
I understand your point.
Previous: Junio C Hamano
Message 3 of 3 in “How to enhance merge commit message ?”
  1. Alexander LitvinovJan 30, 2007
  2. Junio C HamanoJan 30, 2007
  3. Alexander LitvinovJan 30, 2007

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.