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

Re: [PATCH 1/1] Preserve topological ordering after merges This modifies the algorithm of topopological ordering. The problem with the current algoritm is that it displays the graph below as follows

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 7, 2020, 17:01 UTC
Message-ID
<xmqqr20b5hfq.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<nycvar.QRO.7.76.6.2001071305330.46@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 6 quoted lines
> Hi Sergey,
>
> please note that the commit message's first line should not be longer than
> 76 characters per line, and it should be followed by an empty line. I
> think that you forgot the empty line, looking at
> https://github.com/gitgitgadget/git/pull/514/commits/542a02020c8578d0e004cb9c929bced8719b902a
Thanks for a good suggestion.

Also, please do *not* CC iterations of a patch to me that hasn't seen a concensus that it is a good idea on the list yet, unless you know I am the area expert and am interested in seeing it.

Thanks.
Previous: Johannes SchindelinNext: Sergey Rudyshin
Message 4 of 11 in “Preserve topological ordering after merges”
  1. 0/1 Preserve topological ordering after mergesSergey Rudyshin via GitGitGadget, Jan 7, 2020
  2. 1/1 Preserve topological ordering after merges This modifies the algorithm of topopological ordering. The problem with the current algoritm is that it displays the graph below as followsSergey Rudyshin via GitGitGadget, Jan 7, 2020
  3. Johannes SchindelinJan 7, 2020
  4. Junio C HamanoJan 7, 2020
  5. Sergey RudyshinJan 8, 2020
  6. Derrick StoleeJan 7, 2020
  7. Sergey RudyshinJan 8, 2020
  8. Johannes SchindelinJan 7, 2020
  9. Sergey RudyshinJan 8, 2020
  10. Derrick StoleeJan 8, 2020
  11. Sergey RudyshinJan 8, 2020

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.