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

Re: [PATCH 2/2] send-pack: tighten remote error reporting

From
Jeff King <peff@peff.net>
Date
Nov 18, 2007, 07:59 UTC
Message-ID
<20071118075908.GA24972@sigill.intra.peff.net>
In-Reply-To
<20071118071651.GB18467@sigill.intra.peff.net>
On Sun, Nov 18, 2007 at 02:16:52AM -0500, Jeff King wrote:
> +			print_ref_status('!', "[remote rejected]", ref,
> +					ref->deletion ? ref->peer_ref : NULL,
> +					ref->remote_status);
Gah, that should of course be:
  ref->deletion ? NULL : ref->peer_ref
> +		case REF_STATUS_EXPECTING_REPORT:
> +			print_ref_status('!', "[remote failure]", ref,
> +					ref->deletion ? ref->peer_ref : NULL,
> +					"remote failed to report status");
And the same here.

I had resisted making a test that checked the exact output format, because such things are often a pain to keep up to date. But that's two regressions in patches I've submitted that would have been caught. Maybe I should just pay more attention.

-Peff
Previous: Jeff KingNext: Jeff King
Message 6 of 7 in “send-pack: improve error reporting for total remote unpack”
  1. send-pack: improve error reporting for total remote unpackJeff King, Nov 18, 2007
  2. Jeff KingNov 18, 2007
  3. Jeff KingNov 18, 2007
  4. 1/2 make "find_ref_by_name" a public functionJeff King, Nov 18, 2007
  5. 2/2 send-pack: tighten remote error reportingJeff King, Nov 18, 2007
  6. Jeff KingNov 18, 2007
  7. 3/2 send-pack: fix "everything up-to-date" messageJeff King, Nov 18, 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.