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

Re: [PATCH] fetch-pack.c: show correct command name that fails

From
Jeff King <peff@peff.net>
Date
Sep 18, 2013, 18:20 UTC
Message-ID
<20130918182052.GB18821@sigill.intra.peff.net>
In-Reply-To
<xmqqvc1yuhao.fsf@gitster.dls.corp.google.com>
On Wed, Sep 18, 2013 at 11:16:15AM -0700, Junio C Hamano wrote:
Show 6 quoted lines
> I wondered if this is something we can have a test for easily.
> Unlike the "--upload-pack" option, there is no way for the receiving
> end to choose which index-pack (or unpack-objects) to run, but we
> may force a failure by temporarily futzing with PATH to make a dummy
> git-index-pack that always fails to be found or something silly like
> that.

You can feed a bogus pack, which will cause either to fail reliably. I'm not sure if that counts as "easy" though. :) Munging PATH is probably simpler.

> >  fetch-pack.c | 10 +++++-----
> >  1 file changed, 5 insertions(+), 5 deletions(-)
Patch looks good to me, too.
-Peff
Previous: Junio C Hamano
Message 3 of 3 in “fetch-pack.c: show correct command name that fails”
  1. fetch-pack.c: show correct command name that failsNguyễn Thái Ngọc Duy, Sep 18, 2013
  2. Junio C HamanoSep 18, 2013
  3. Jeff KingSep 18, 2013

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.