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

Re: On the nature of cover letters [WAS Re: [PATCH 0/6] Create Git/Packet.pm]

From
Stefan Beller <sbeller@google.com>
Date
Nov 1, 2017, 22:31 UTC
Message-ID
<CAGZ79kYghF6=AzL1N96fe2zixHCERXu=RpxHw2-kdUrU+j4CXw@mail.gmail.com>
In-Reply-To
<CAGZ79kYKK69Xw0-2OxFpo9Q=Kv1hvw8D7YkfhMFFcgzTuevTCQ@mail.gmail.com>
On Wed, Nov 1, 2017 at 9:42 AM, Stefan Beller <sbeller@google.com> wrote:
Show 9 quoted lines
>> So it may make more sense just to cross-reference those merges with the
>> topics that spawned them on the mailing list. I.e., instead of copying
>> the cover letter contents, just record the message-id (and update it
>> whenever a new iteration of a topic is picked up via "git am"). That
>> lets you get the cover letter information _and_ see any discussion
>> or review around the patch.
>
> That sounds good.
>

Actually I just found out about `am.messageId`, which adds the individual message id as a footer. Maybe that is good enough? (Though it would clutter every commit, not just the merge commits)

Previous: Stefan BellerNext: Jeff King
Message 4 of 8 in “On the nature of cover letters [WAS Re: [PATCH 0/6] Create Git/Packet.pm]”
  1. Stefan BellerOct 30, 2017
  2. Jeff KingNov 1, 2017
  3. Stefan BellerNov 1, 2017
  4. Stefan BellerNov 1, 2017
  5. Jeff KingNov 2, 2017
  6. Junio C HamanoNov 2, 2017
  7. Jeff KingNov 2, 2017
  8. Stefan BellerNov 2, 2017

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.