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

[PATCH 2/2] Fixes a problem with --merge-order A B (A is linear descendent of a merge B)

From
Jon Seymour <jon.seymour@gmail.com>
Date
Jul 6, 2005, 14:44 UTC
Message-ID
<20050706144408.17769.qmail@blackcubes.dyndns.org>
This patch passes the test case in the first patch of this series.
Signed-off-by: Jon Seymour <jon.seymour@gmail.com>
---
 epoch.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
e4f793b932b30a7bee16610e311630515fe88330
diff --git a/epoch.c b/epoch.c
--- a/epoch.c
+++ b/epoch.c
@@ -612,7 +612,7 @@ int sort_list_in_merge_order(struct comm
 		while (reversed) {
 			struct commit * next = pop_commit(&reversed);
 
-			if (!(next->object.flags & VISITED)) {
+			if (!(next->object.flags & VISITED) && next!=base) {
 				sort_first_epoch(next, &stack);
 				if (reversed) {
 					/*
------------
Message 1 of 1 in “Fixes a problem with --merge-order A B (A is linear descendent of a merge B)”
  1. 2/2 Fixes a problem with --merge-order A B (A is linear descendent of a merge B)Jon Seymour, Jul 6, 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.