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

[PATCH v2 1/3] revision: "simplify" options imply topo-order sort

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 22, 2012, 22:27 UTC
Message-ID
<1340404061-11619-2-git-send-email-gitster@pobox.com>
In-Reply-To
<1340404061-11619-1-git-send-email-gitster@pobox.com>
The code internally runs sort_in_topo_order() already; it is more clear
to spell it out in the option parsing phase, instead of adding a special
case in simplify_merges() function.
---
 revision.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/revision.c b/revision.c
index 935e7a7..00aaefe 100644
--- a/revision.c
+++ b/revision.c
@@ -1358,11 +1358,13 @@ static int handle_revision_opt(struct rev_info *revs, int argc, const char **arg
 		revs->topo_order = 1;
 	} else if (!strcmp(arg, "--simplify-merges")) {
 		revs->simplify_merges = 1;
+		revs->topo_order = 1;
 		revs->rewrite_parents = 1;
 		revs->simplify_history = 0;
 		revs->limited = 1;
 	} else if (!strcmp(arg, "--simplify-by-decoration")) {
 		revs->simplify_merges = 1;
+		revs->topo_order = 1;
 		revs->rewrite_parents = 1;
 		revs->simplify_history = 0;
 		revs->simplify_by_decoration = 1;
@@ -2016,8 +2018,6 @@ static void simplify_merges(struct rev_info *revs)
 	struct commit_list *list;
 	struct commit_list *yet_to_do, **tail;
 
-	if (!revs->topo_order)
-		sort_in_topological_order(&revs->commits, revs->lifo);
 	if (!revs->prune)
 		return;
 
-- 
1.7.11.1.29.gf71be5c
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 4 in “"log --first-parent --simplify-merges/by-decoration"”
  1. 0/3 "log --first-parent --simplify-merges/by-decoration"Junio C Hamano, Jun 22, 2012
  2. 1/3 revision: "simplify" options imply topo-order sortJunio C Hamano, Jun 22, 2012
  3. 2/3 revision: note the lack of free() in simplify_merges()Junio C Hamano, Jun 22, 2012
  4. 3/3 revision: ignore side parents while running simplify-mergesJunio C Hamano, Jun 22, 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.