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

Re: "--quiet" for git-push does not suppress remote hook output

From
LELaszlo Ersek <lersek@redhat.com>
Date
May 7, 2020, 12:16 UTC
Message-ID
<3cb011a9-ce3d-df38-01c6-062062f1c9c2@redhat.com>
In-Reply-To
<ba70b25b-906c-0117-2594-c606595c6816@redhat.com>
(Sorry about the self-followup...)
On 05/07/20 14:05, Laszlo Ersek wrote:
Show 12 quoted lines
> Hi,
> 
> being a total novice in git internals, it seems like
> "builtin/receive-pack.c" (on the server) forwards any receive hook
> output with copy_to_sideband() back to git-push (on the client), even if
> git-push was invoked with "--quiet".
> 
> And "case 2" in demultiplex_sideband() seems to print that "band" to
> stderr (on the client), despite "--quiet".
> 
> Is this intentional? I'd prefer "git push --quiet" to suppress remote
> hook output (unless the remote hook fails).
Or else:

would it be the job of the particular receive hooks to observe and obey the "--quiet" option in the GIT_PUSH_OPTION_* environment variables?

Thanks! Laszlo

Previous: Laszlo ErsekNext: Jeff King
Message 2 of 4 in “"--quiet" for git-push does not suppress remote hook output”
  1. Laszlo ErsekMay 7, 2020
  2. Laszlo ErsekMay 7, 2020
  3. Jeff KingMay 7, 2020
  4. Laszlo ErsekMay 8, 2020

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.