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

Re: [PATCH] Restore expected list order for --merge-order switch

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jul 5, 2005, 23:21 UTC
Message-ID
<2cfc403205070516216b911160@mail.gmail.com>
In-Reply-To
<20050705010619.13581.qmail@blackcubes.dyndns.org>
G'day Linus,
Is there some reason why this didn't get applied?
jon.
On 7/5/05, Jon Seymour <jon.seymour@gmail.com> wrote:
Show 15 quoted lines
> 
> A recent change to rev-list altered the order in which start points
> are presented to the merge-order sort algorithm. This caused
> breaks in the t/t6001 unit tests.
> 
> This change restores the order in which start points are presented to the
> the merge-order sort algorithm (but leaves the order unchanged from
> the immediately preceding behaviour for non --merge-order sorts).
> 
> The order in which arguments are presented to the merge-order
> sort algorithm is significant, since left-most arguments
> are expected to sort last so as to be consistent with
> how left-most parents sort.
> 
> Signed-off-by: Jon Seymour <jon.seymour@gmail.com>
Previous: Jon SeymourNext: Linus Torvalds
Message 2 of 3 in “Restore expected list order for --merge-order switch”
  1. Restore expected list order for --merge-order switchJon Seymour, Jul 5, 2005
  2. Jon SeymourJul 5, 2005
  3. Linus TorvaldsJul 5, 2005

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.