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

[PATCH/RFC 2/3] send-pack: check ref->status before updating tracking refs

From
Jeff King <peff@peff.net>
Date
Nov 13, 2007, 10:27 UTC
Message-ID
<20071113102757.GB2905@sigill.intra.peff.net>
In-Reply-To
<20071113102500.GA2767@sigill.intra.peff.net>
Previously, we manually checked the 'NONE' and 'UPTODATE'
conditions. Now that we have ref->status, we can easily
say "only update if we pushed successfully".
---
 builtin-send-pack.c |   15 ++++-----------
 1 files changed, 4 insertions(+), 11 deletions(-)
diff --git a/builtin-send-pack.c b/builtin-send-pack.c
index 3ac2615..2805c92 100644
--- a/builtin-send-pack.c
+++ b/builtin-send-pack.c
@@ -180,24 +180,17 @@ static int receive_status(int in)
 static void update_tracking_ref(struct remote *remote, struct ref *ref)
 {
 	struct refspec rs;
-	int will_delete_ref;
 
-	rs.src = ref->name;
-	rs.dst = NULL;
-
-	if (!ref->peer_ref)
+	if (ref->status != REF_STATUS_OK)
 		return;
 
-	will_delete_ref = is_null_sha1(ref->peer_ref->new_sha1);
-
-	if (!will_delete_ref &&
-			!hashcmp(ref->old_sha1, ref->peer_ref->new_sha1))
-		return;
+	rs.src = ref->name;
+	rs.dst = NULL;
 
 	if (!remote_find_tracking(remote, &rs)) {
 		if (args.verbose)
 			fprintf(stderr, "updating local tracking ref '%s'\n", rs.dst);
-		if (is_null_sha1(ref->peer_ref->new_sha1)) {
+		if (ref->deletion) {
 			if (delete_ref(rs.dst, NULL))
 				error("Failed to delete");
 		} else
-- 
1.5.3.5.1704.g24d42-dirty
Previous: Alex RiesenNext: Jeff King
Message 7 of 20 in “tracking per-ref errors on push”
  1. 0/3 tracking per-ref errors on pushJeff King, Nov 13, 2007
  2. 1/3 send-pack: track errors for each refJeff King, Nov 13, 2007
  3. Jeff KingNov 13, 2007
  4. Alex RiesenNov 13, 2007
  5. Jeff KingNov 13, 2007
  6. Alex RiesenNov 13, 2007
  7. 2/3 send-pack: check ref->status before updating tracking refsJeff King, Nov 13, 2007
  8. 3/3 send-pack: assign remote errors to each refJeff King, Nov 13, 2007
  9. Jeff KingNov 13, 2007
  10. Jeff KingNov 13, 2007
  11. 1/3 send-pack: track errors for each refJeff King, Nov 13, 2007
  12. 2/3 send-pack: check ref->status before updating tracking refsJeff King, Nov 13, 2007
  13. 3/3 send-pack: assign remote errors to each refJeff King, Nov 13, 2007
  14. Junio C HamanoNov 14, 2007
  15. Junio C HamanoNov 14, 2007
  16. Johannes SchindelinNov 14, 2007
  17. Junio C HamanoNov 14, 2007
  18. Jeff KingNov 15, 2007
  19. Junio C HamanoNov 16, 2007
  20. Jeff KingNov 15, 2007

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.