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

Re: merge summaries

From
Junio C Hamano <junkio@cox.net>
Date
May 19, 2007, 19:24 UTC
Message-ID
<7vy7jkwr96.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<73A1C4C5-50E9-4844-85F8-00D99682B6D4@zib.de>
Steffen Prohaska <prohaska@zib.de> writes:
Show 6 quoted lines
> What is so wrong if merge summaries of pulls from you were committed
> to topic branches. Later when you pull such branches the summaries
> shouldn't be a problem. A short-log of the topic branch wouldn't
> contain the summaries.
>
> Probably I do not fully understand what "the wrong way around" means.
I think you understand it very well.

As long as you stay as a "pull-only" person, and will never ask the upstream to pull back from you, what first parent log would show would make perfectly good sense. However, once a pull from you by the upstream happens, the resulting history would get the summary in the merge you did, which is totally unwanted --- the upstream already had those summarized commits long time ago in its history.

Previous: Steffen ProhaskaNext: Junio C Hamano
Message 14 of 18 in “merge summaries”
  1. Steffen ProhaskaMay 18, 2007
  2. Linus TorvaldsMay 18, 2007
  3. Junio C HamanoMay 18, 2007
  4. Linus TorvaldsMay 18, 2007
  5. J. Bruce FieldsMay 18, 2007
  6. Linus TorvaldsMay 18, 2007
  7. Junio C HamanoMay 18, 2007
  8. Robin RosenbergMay 20, 2007
  9. rev-list: '--indent' oneline outputSteffen Prohaska, May 20, 2007
  10. Steffen ProhaskaMay 20, 2007
  11. Junio C HamanoMay 20, 2007
  12. Steffen ProhaskaMay 20, 2007
  13. Steffen ProhaskaMay 19, 2007
  14. Junio C HamanoMay 19, 2007
  15. Junio C HamanoMay 19, 2007
  16. Steffen ProhaskaMay 20, 2007
  17. Junio C HamanoMay 20, 2007
  18. Junio C HamanoMay 20, 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.