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
Apr 4, 2007, 06:24 UTC
Message-ID
<7v7iss8xo6.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20070404060213.GB31984@mellanox.co.il>
"Michael S. Tsirkin" <mst@dev.mellanox.co.il> writes:
Show 63 quoted lines
> Quoting Junio C Hamano <junkio@cox.net>:
> Subject: Re: [PATCH] have merge put FETCH_HEAD data in commit message
>
>> "Michael S. Tsirkin" <mst@dev.mellanox.co.il> writes:
>> 
>> >> > 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?
>> >
>> > Looks good. What about 3?
>> 
>> When e-mailed message has garbage at the beginning (e.g. "Hi!"),
>> git users can either run "commit --amend" immiediately after
>> "git am",
>
> This one would overwrite the authorship information though,
> would it not? I actually wished several times for an --amend-message
> commit flag that would only edit the message, preserving the author
> (and possibly date?) metadata.
> Of course, I simply copy the author and pass it in --author,
> but it's somewhat awkward to do. Do others notice this?
>
> *Maybe* git can be even smarter, and notice that only
> commit message has changed, and preserve the author automatically
> in this case? I haven't looked at how hard that would be to do.
>
> <rant>
> I actually find it awkward that author/summary information is never
> shown during git commit - sometimes one does git commit
> on a machine where GIT_AUTHOR_EMAIL has not been setup
> correctly, and the result often is mst@mst-desktop.(none).
> Or people sometimes forget that the first line will show up
> in the pretty=short summary and the result is that what
> ends up being there is just 2 first lines of the long description.
>
> One has to remember to always do git log --pretty=short
> after commit to verify that one did get these details right.
>
> Ideas:
> - Maybe have git-commit display shortlog summary for commit just created?
> - Maybe put Author: (or From:? and maybe Subject:?) line in the pre-formatted
>   commit message, and let the user edit them?
> </rant>
>
>> or edit the mbox with editor before running
>> "applymbox", so the need has not been felt much us, and that is
>> the primary reason why it is not there.  Additionally we do not
>> think it is particularly a good practice to have "cover letters"
>> at the top (cf. $gmane/5418), so it was never high priority for
>> us to add that feature to encourage such a practice.
>> 
>> Having said that, on top of the recent work by Don Zickus on
>> mailinfo, you _could_ add support for scissors "^-- >8 --$" if
>> you want.
>
> OK, I thought about this a bit - if the message includes a
> cover letter, I think it's also likely to have an incorrect
> subject too. So how about simply ignoring text before
> Subject:/From: lines? This makes more sense, for me, than
> inventing yet another git-specific convention. Does this for you?
People sometimes say something like:
    From: Quim K Holland <qkholland@cox.net>
    Date: Wed, 4 Apr 2007 09:02:13 +0300
    Subject: [PATCH] Fix frobnitz while nitfol is in use
    Message-Id: <20070404060213.GB31984@filfre.cox.net>
    Earlier Sloof Lirpa reported that frobnitz feature has problems
    when nitfol is running background in this message:
    From: Sloof Lirpa <sitemaster@cox.net>
    Subject: [BUG] frobnitz garbles its output
    Message-Id: <20070403060213.GB31984@frotz.cox.net>
    Upon closer inspection, the problem is caused by filfre
    function firing up prematurely because nitfol process grabs
    semaphore and never releases it.  Here is a patch to fix
    this issue...
    Signed-off-by: Quim K Holland <qkholland@cox.net>
    ---
    diff --git a/... b/...

And that is why we do not even pick up the From: and stuff in the middle of the message.

We might be able to convince people to adopt a convention to use an explicit mark to signal the end of cover letter (or maybe make it an option in .git/config), but one thing we do not absolutely want to do is to pick up "^(From|Date|Subject): " from any random place in the middle of message, let alone discarding what comes before them.

That is, something like the following might be acceptable instead:

    From: Sloof Lirpa <sitemaster@cox.net>
    Subject: [BUG] frobnitz garbles its output
    Message-Id: <20070403060213.GB31984@frotz.cox.net>
    Quim K Holland's patch fixes the problem I reported earlier,
    so I am forwarding his patch.  Please apply.
    -- >8 --
    From: Quim K Holland <qkholland@cox.net>
    Date: Wed, 4 Apr 2007 09:02:13 +0300
    Subject: [PATCH] Fix frobnitz while nitfol is in use
    Message-Id: <20070404060213.GB31984@filfre.cox.net>
    Earlier Sloof Lirpa reported that frobnitz feature has problems
    when nitfol is running background in this message:
    Upon closer inspection, the problem is caused by filfre
    function firing up prematurely because nitfol process grabs
    semaphore and never releases it.  Here is a patch to fix
    this issue...
    Signed-off-by: Quim K Holland <qkholland@cox.net>
    ---
    diff --git a/... b/...
Previous: Shawn O. PearceNext: Michael S. Tsirkin
Message 19 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.