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
MTMichael S. Tsirkin <mst@dev.mellanox.co.il>
Date
Mar 22, 2007, 08:37 UTC
Message-ID
<20070322083757.GC29341@mellanox.co.il>
In-Reply-To
<7vlkhpvgc7.fsf@assigned-by-dhcp.cox.net>
Show 5 quoted lines
> (2) ... In other
>     words, *users* of git-am are not supposed to figure it out.
>     They will not find *their* project policy from git
>     documentation, unless their project happens to be the git
>     project.

But if they don't use the same formatting as git policy requires, git-am will produce a mess of a log, until they discover the only policy that works with git-am by word of mouth.

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)
Show 5 quoted lines
> (3) However, we are discussing your patch to support "git merge
>     FETCH_HEAD" better, which I took as your contribution to the
>     git project.  I asked you to follow the project policy for
>     your contribution, and pointed at the document that
>     describes the policy.
Amen to that, sorry about the formatting.
Show 15 quoted lines
> To reiterate the more important points (this is also for my own
> purpose because I do not want the patch lost in this noise we
> are making):
> 
>  - Checking readability of $GIT_DIR/$remote itself is too loose;
>    the name FETCH_HEAD should explicitly be checked, as that is
>    the file that has the specific format that is understood by
>    fmt-merge-msg.
> 
>  - "echo -n" is to be avoided for portability.
> 
>  - "git fetch $URL foo bar" would leave two lines in FETCH_HEAD;
>    subsequent "git merge FETCH_HEAD" would merge only foo.  Pick
>    the first line, stripping out not-for-merge marker and let it
>    processed by fmt-merge-msg.
Thanks, I'll try to address these.
-- 
MST
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 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.