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

[PATCH v2 3/7] Ensure tail pointer gets setup correctly when we fetch HEAD only

From
Shawn O. Pearce <spearce@spearce.org>
Date
Mar 1, 2008, 05:24 UTC
Message-ID
<20080301052459.GC27300@spearce.org>

If we ever decided to append onto the end of this list the tail pointer must be looking at the right memory cell at the end of the HEAD ref_map.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---
 builtin-fetch.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/builtin-fetch.c b/builtin-fetch.c
index 1348a0e..5bce20f 100644
--- a/builtin-fetch.c
+++ b/builtin-fetch.c
@@ -157,6 +157,7 @@ static struct ref *get_ref_map(struct transport *transport,
 			if (!ref_map)
 				die("Couldn't find remote ref HEAD");
 			ref_map->merge = 1;
+			tail = &ref_map->next;
 		}
 	}
 	ref_remove_duplicates(ref_map);
-- 
1.5.4.3.409.g88113
Message 1 of 1 in “Ensure tail pointer gets setup correctly when we fetch HEAD only”
  1. 3/7 Ensure tail pointer gets setup correctly when we fetch HEAD onlyShawn O. Pearce, Mar 1, 2008

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.