Re: [PATCH 2/2] transport: don't ignore git-receive-pack(1) exit code on atomic push

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 14, 2024, 23:36 UTC
Message-ID: <xmqqsert5qx7.fsf@gitster.g>
In-Reply-To: <CANYiYbHGdJsTgdzJj1r4sPdTAcZCf3C-qA538fcXbD1jjB1BUw@mail.gmail.com>

Jiang Xin <worldhello.net@gmail.com> writes:

> If we want to print "Done" in porcelain mode when there are no
> errors. (In dry run mode, ref-update-errors should not be
> considered as errors, but the opposite should be regarded as errors).

Hmph, should we allow dry-run to deliberately behave differently from the for-real execution? Wouldn't it discard the primary value of dry-run, to see if it is likely that an operation will succeed (or fail)?

$ 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.