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

Re: [PATCH/RFC] fmt-merge-msg: add a blank line after people info

From
Junio C Hamano <gitster@pobox.com>
Date
May 16, 2012, 17:28 UTC
Message-ID
<7vpqa4c9wr.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CA+55aFyX66RpUA2Xh8drGErHB7Wuni20cUAMGawLsqG6MTTohA@mail.gmail.com>
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 15 quoted lines
> On Tue, May 15, 2012 at 1:24 PM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Now, computing this efficiently may not be trivial, as you would need N^2
>> reachability analysis when pulling in N commits. Among 2000 recent merges
>> I sampled from the kernel history, 70+ pull in more than 1000 commits (the
>> largest one d4bbf7e77 pulls in 21k commits).
>
> So I have to say, for my purposes, it not only might be inefficient,
> but it can still be very misleading.
> ...
> (Admittedly, so it the shortlog we put in the merge, so that "you can
> find it later in the git tree itself" not *that* great of an argument
> - the real argument for me is that it doesn't matter what you count,
> you'll not necessarily get the actual piece of information I care
> about..).

There is no way to mine "X pulled from Y" out of the topology if you allow fast-forward anywhere, so "I care about whom I pulled from" is something people need to give out of band. Your lieutenant may have fast-forwarded his history from his lieutenant's, or you may even be fast-forwarding your history from your lieutenant's, in which case you do not even have a merge commit to record that fact anyway. If you do not fast-forward, at least the merge subject would give you where you got the history from, so it is not like that the information *must* be obtained by looking at the history anyway (incidentally, that was the reason why the "better than random number generator but not by a large margin" version gives an extra weight to the tip commit you are pulling; unless your lieutenant fast-forwarded, that is the person you pulled from).

> So I'm not entirely convinced yet. I don't *dislike* the concept, but
> I could definitely do without it (or maybe have it in the commented
> part of the commit message, so that you'd have to explicitly edit it
> to show up).

I am tempted to suggest removing the "via" part as a failed experiment for now.

Previous: Linus TorvaldsNext: Jonathan Nieder
Message 32 of 36 in “A possible fmt-merge-msg update?”
  1. Junio C HamanoMar 5, 2012
  2. Linus TorvaldsMar 5, 2012
  3. Junio C HamanoMar 5, 2012
  4. Linus TorvaldsMar 5, 2012
  5. fmt-merge-msg: show those involved in a merged seriesJunio C Hamano, Mar 5, 2012
  6. Linus TorvaldsMar 5, 2012
  7. Junio C HamanoMar 5, 2012
  8. René ScharfeMar 7, 2012
  9. Junio C HamanoMar 7, 2012
  10. René ScharfeMar 8, 2012
  11. Junio C HamanoMar 8, 2012
  12. Junio C HamanoMar 8, 2012
  13. Phil HordMar 12, 2012
  14. Jeff KingMar 13, 2012
  15. Junio C HamanoMar 14, 2012
  16. Phil HordMar 14, 2012
  17. Jonathan NiederMar 12, 2012
  18. Junio C HamanoMar 13, 2012
  19. Jonathan NiederMar 13, 2012
  20. Junio C HamanoMar 13, 2012
  21. Johannes SixtMar 13, 2012
  22. Junio C HamanoMar 13, 2012
  23. Johannes SixtMar 14, 2012
  24. Junio C HamanoMar 14, 2012
  25. 1/1 fmt-merge-msg: show those involved in a merged seriesJunio C Hamano, Mar 13, 2012
  26. fmt-merge-msg: add a blank line after people infoJonathan Nieder, May 11, 2012
  27. Junio C HamanoMay 11, 2012
  28. Linus TorvaldsMay 11, 2012
  29. Junio C HamanoMay 14, 2012
  30. Junio C HamanoMay 15, 2012
  31. Linus TorvaldsMay 16, 2012
  32. Junio C HamanoMay 16, 2012
  33. Jonathan NiederJun 6, 2012
  34. Jonathan NiederJun 6, 2012
  35. Junio C HamanoJun 6, 2012
  36. Jeff KingMar 6, 2012

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.