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

Re: [PATCH] have merge put FETCH_HEAD data in commit message

From
Junio C Hamano <junkio@cox.net>
Date
Mar 22, 2007, 10:31 UTC
Message-ID
<7vr6rhtvr0.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070322083757.GC29341@mellanox.co.il>
"Michael S. Tsirkin" <mst@dev.mellanox.co.il> writes:
Show 9 quoted lines
> Specifically, as far as a *user* is concerned:
> 1. the fact that "---" separates commit message from patch, and
>    that text after "---" is ignored seems to be undocumented
> 2. the fact that message subject is appended to the log,
>    the rules for removing [PATCH] etc from subject seem to be undocumented
> 3. if I want to have some text coming *before* the commit
>    message ignored, there's no way to do this
> 4. there's no way to override the subject from within the message
>    (like there is with author/From line)

How about this? Also check t5100 and its sample mailbox, especially the "third patch" from A U Thor, which I forwarded with the subject "another patch".

---
 Documentation/git-am.txt |   27 +++++++++++++++++++++++++++
 1 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-am.txt b/Documentation/git-am.txt
index 13a7389..148ce40 100644
--- a/Documentation/git-am.txt
+++ b/Documentation/git-am.txt
@@ -87,6 +87,33 @@ default.   You could use `--no-utf8` to override this.
 DISCUSSION
 ----------
 
+The commit author name is taken from the "From: " line of the
+message, and commit author time is taken from the "Date: " line
+of the message.  The "Subject: " line is used as the title of
+the commit, after stripping common prefix "[PATCH <anything>]".
+It is supposed to describe what the commit is about concisely as
+a one line text.
+
+The body of the message (iow, after a blank line that terminates
+RFC2822 headers) can begin with "Subject: " and "From: " lines
+that are different from those of the mail header, to override
+the values of these fields.
+
+The commit message is formed by the title taken from the
+"Subject: ", a blank line and the body of the message up to
+where the patch begins.  Excess whitespaces at the end of the
+lines are automatically stripped.
+
+The patch is expected to be inline, directly following the
+message.  Any line that is of form:
+
+* three-dashes and end-of-line, or
+* a line that begins with "diff -", or
+* a line that begins with "Index: "
+
+is taken as the beginning of a patch, and the commit log message
+is terminated before the first occurrence of such a line.
+
 When initially invoking it, you give it names of the mailboxes
 to crunch.  Upon seeing the first patch that does not apply, it
 aborts in the middle, just like 'git-applymbox' does.  You can
Previous: Michael S. TsirkinNext: Michael S. Tsirkin
Message 10 of 70 in “have merge put FETCH_HEAD data in commit message”
  1. have merge put FETCH_HEAD data in commit messageMichael S. Tsirkin, Mar 21, 2007
  2. Junio C HamanoMar 21, 2007
  3. Michael S. TsirkinMar 22, 2007
  4. Junio C HamanoMar 22, 2007
  5. Michael S. TsirkinMar 22, 2007
  6. Junio C HamanoMar 22, 2007
  7. Michael S. TsirkinMar 22, 2007
  8. Junio C HamanoMar 22, 2007
  9. Michael S. TsirkinMar 22, 2007
  10. Junio C HamanoMar 22, 2007
  11. Michael S. TsirkinMar 22, 2007
  12. Junio C HamanoMar 24, 2007
  13. Michael S. TsirkinApr 4, 2007
  14. Junio C HamanoApr 4, 2007
  15. Michael S. TsirkinApr 4, 2007
  16. Shawn O. PearceApr 4, 2007
  17. Junio C HamanoApr 4, 2007
  18. Shawn O. PearceApr 4, 2007
  19. Junio C HamanoApr 4, 2007
  20. display shortlog after git-commitMichael S. Tsirkin, Apr 4, 2007
  21. Junio C HamanoApr 4, 2007
  22. display shortlog after git-commitMichael S. Tsirkin, Apr 15, 2007
  23. Junio C HamanoApr 15, 2007
  24. display the subject of the commit just madeMichael S. Tsirkin, Apr 16, 2007
  25. Junio C HamanoApr 16, 2007
  26. Michael S. TsirkinApr 16, 2007
  27. Junio C HamanoApr 16, 2007
  28. Michael S. TsirkinApr 16, 2007
  29. Junio C HamanoApr 16, 2007
  30. Michael S. TsirkinApr 16, 2007
  31. Michael S. TsirkinApr 16, 2007
  32. Junio C HamanoApr 16, 2007
  33. Shawn O. PearceApr 16, 2007
  34. Michael S. TsirkinApr 16, 2007
  35. Alex RiesenApr 16, 2007
  36. Junio C HamanoApr 16, 2007
  37. Michael S. TsirkinApr 16, 2007
  38. Junio C HamanoApr 16, 2007
  39. Michael S. TsirkinApr 16, 2007
  40. remove shortlog from git-commit outputMichael S. Tsirkin, Apr 16, 2007
  41. Julian PhillipsApr 16, 2007
  42. Michael S. TsirkinApr 16, 2007
  43. Julian PhillipsApr 16, 2007
  44. Michael S. TsirkinApr 17, 2007
  45. Julian PhillipsApr 17, 2007
  46. Junio C HamanoApr 4, 2007
  47. Michael S. TsirkinApr 15, 2007
  48. Junio C HamanoApr 15, 2007
  49. Michael S. TsirkinApr 15, 2007
  50. Andy ParkinsApr 15, 2007
  51. Michael S. TsirkinApr 15, 2007
  52. wt-status: show author info if status.showauthor is setJeff King, Apr 4, 2007
  53. Junio C HamanoApr 4, 2007
  54. Michael S. TsirkinApr 4, 2007
  55. Junio C HamanoApr 4, 2007
  56. Shawn O. PearceApr 4, 2007
  57. Jakub NarebskiApr 4, 2007
  58. Jakub NarebskiMar 23, 2007
  59. J. Bruce FieldsMar 23, 2007
  60. Jakub NarebskiMar 23, 2007
  61. J. Bruce FieldsMar 23, 2007
  62. Jakub NarebskiMar 24, 2007
  63. Put FETCH_HEAD data in merge commit messageMichael S. Tsirkin, Mar 22, 2007
  64. Junio C HamanoMar 22, 2007
  65. Jeff KingMar 22, 2007
  66. Junio C HamanoMar 22, 2007
  67. Jeff KingMar 22, 2007
  68. Andy ParkinsMar 22, 2007
  69. [PATCHv2] put FETCH_HEAD data in merge commit messageMichael S. Tsirkin, Mar 21, 2007
  70. Junio C HamanoMar 21, 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.