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

Re: Git sideband hook output

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jun 8, 2010, 21:46 UTC
Message-ID
<20100608214632.GN14847@spearce.org>
In-Reply-To
<AANLkTinLWDFTn7bhcF3Vk-q9aw4lJC2vFj95M9bxLbBT@mail.gmail.com>
Scott Chacon <schacon@gmail.com> wrote:
> Prior to 6d525d where Shawn made the receive-pack process send hook
> output over side band #2, how did the hook output get sent to the
> client?

It was sent over stderr, which was proxied down to the client by the SSH daemon.

> On older clients (before this commit) and on older servers,
> the hook output just shows up without the 'remote:' prefix.

Because its echoed to the tty by the SSH client, without Git ever seeing it.

> After
> this commit I get the 'remote:' prefix,

Now its being parsed out of the stream by the git client, using the same code that displays the progress messages during clone/fetch.

> which is kind of annoying.

Depends on your perspective. Its nice to know that the messages came from the server, rather than from your client. :-)

> Is
> there a way to suppress this to get the old output format?
No.  Other than to have the hook not output anything at all.
-- 
Shawn.
Previous: Scott ChaconNext: Peter Kjellerstedt
Message 2 of 17 in “Git sideband hook output”
  1. Scott ChaconJun 8, 2010
  2. Shawn O. PearceJun 8, 2010
  3. Peter KjellerstedtJun 9, 2010
  4. Nicolas PitreJun 9, 2010
  5. Peter KjellerstedtJun 10, 2010
  6. Nicolas PitreJun 10, 2010
  7. Shawn O. PearceJun 10, 2010
  8. Scott ChaconJun 10, 2010
  9. PJ HyettJun 11, 2010
  10. Wincent ColaiutaJun 11, 2010
  11. Erik Faye-LundJun 11, 2010
  12. Junio C HamanoJun 11, 2010
  13. Jeff KingJun 12, 2010
  14. A Large Angry SCMJun 11, 2010
  15. Ævar Arnfjörð BjarmasonJun 11, 2010
  16. A Large Angry SCMJun 11, 2010
  17. Johannes SixtJun 9, 2010

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.