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

[RFC] series headers

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jul 10, 2007, 06:14 UTC
Message-ID
<Pine.LNX.4.64.0707100126250.6977@iabervon.org>

I'd like to be able to get format-patch to produce a [PATCH 0/N] message, with a message that's actually in my repository, plus various goodies generated either from diffing the ends of the series or by running through the log an extra time to pick up summary information.

The second best idea I have for this currently is to have a commit at the end of the series which specifies which has the same tree as its parent and has a message with a line "Since <sha1 of the first commit of the series>" and has the text. This goes at the end of the series, because it describes the state with all of the changes made, which is only a good description of a commit at the end of the series, not a commit at the start of the series. Making it [PATCH 0/N] is just because it belongs first in presentation, regardless of whether the other commits are presented with recent commits first or last.

The better idea I just had was to have format-patch notice if the "until" side is a tag object instead of a commit, and generate a [0/N] with the tag message.

As far as implementing this... would it be sane to make struct rev_info.commit_format a callback, so that the code to generate an email message can be somewhere that's easy to use to generate an email that isn't for a commit in the log? I don't *think* git's quite fast enough for the indirect jump to a callback instead of an if tree for an enum will actually hurt us.

	-Daniel
*This .sig left intentionally blank*
Next: Junio C Hamano
Message 1 of 11 in “[RFC] series headers”
  1. Daniel BarkalowJul 10, 2007
  2. Junio C HamanoJul 10, 2007
  3. Theodore TsoJul 10, 2007
  4. Johannes SchindelinJul 10, 2007
  5. Theodore TsoJul 10, 2007
  6. Johannes SchindelinJul 10, 2007
  7. Teach the --cover-letter option to format-patchJohannes Schindelin, Jul 10, 2007
  8. Daniel BarkalowJul 10, 2007
  9. Johannes SchindelinJul 10, 2007
  10. Peter OberndorferJul 24, 2007
  11. Daniel BarkalowJul 24, 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.