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

Re: How to use git-fmt-merge-msg?

From
SBSanti Béjar <santi@agolina.net>
Date
Feb 5, 2009, 13:35 UTC
Message-ID
<adf1fd3d0902050535y631035b6lfc09e0982aefdfd7@mail.gmail.com>
In-Reply-To
<B22C0229-47F4-48EC-9C68-63696C7BB3F2@manchester.ac.uk>
2009/2/5 Robert Haines <rhaines@manchester.ac.uk>:
>
> On 5 Feb 2009, at 12:59, Santi Béjar wrote:
>
[...]
Show 14 quoted lines
>>
>> Manpage of git merge:
>>      --log
>>          In addition to branch names, populate the log message with
>> one-line
>>          descriptions from the actual commits that are being merged.
>>
>> Manpage of git config:
>>      merge.log
>>          Whether to include summaries of merged commits in newly created
>>          merge commit messages. False by default.
>
> Aaaahhhh.... Time for me to upgrade. The version of git I am using (1.5.3.8)
> doesn't have merge --log. No wonder I couldn't find it!

In that version you can use --summary and merge.summary, but they are now deprecated.

HTH, Santi

Previous: Robert Haines
Message 4 of 4 in “How to use git-fmt-merge-msg?”
  1. Robert HainesFeb 5, 2009
  2. Santi BéjarFeb 5, 2009
  3. Robert HainesFeb 5, 2009
  4. Santi BéjarFeb 5, 2009

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.