All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Git sideband hook output
Date: Wed, 09 Jun 2010 08:10:47 +0200	[thread overview]
Message-ID: <4C0F3067.9090501@viscovery.net> (raw)
In-Reply-To: <AANLkTinLWDFTn7bhcF3Vk-q9aw4lJC2vFj95M9bxLbBT@mail.gmail.com>

Am 6/8/2010 22:32, schrieb Scott Chacon:
> 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?  On older clients (before this commit) and on older servers,
> the hook output just shows up without the 'remote:' prefix.  After
> this commit I get the 'remote:' prefix, which is kind of annoying.  Is
> there a way to suppress this to get the old output format?  Or a
> recommended way of patching the client/server in future versions to
> get the old format back?

What happens if your git-receive-pack does not announce side-band-64k?

-- Hannes

      parent reply	other threads:[~2010-06-09  6:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 20:32 Git sideband hook output Scott Chacon
2010-06-08 21:46 ` Shawn O. Pearce
2010-06-09  8:04   ` Peter Kjellerstedt
2010-06-09 13:44     ` Nicolas Pitre
2010-06-10 12:56       ` Peter Kjellerstedt
2010-06-10 18:05         ` Nicolas Pitre
2010-06-10 18:30         ` Shawn O. Pearce
2010-06-10 18:49           ` Scott Chacon
2010-06-11 14:34             ` PJ Hyett
2010-06-11 14:45               ` Wincent Colaiuta
2010-06-11 15:11                 ` Erik Faye-Lund
2010-06-11 23:52                   ` Junio C Hamano
2010-06-12  4:07                     ` Jeff King
2010-06-11 21:54                 ` A Large Angry SCM
2010-06-11 15:18           ` Ævar Arnfjörð Bjarmason
2010-06-11 21:55             ` A Large Angry SCM
2010-06-09  6:10 ` Johannes Sixt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C0F3067.9090501@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=schacon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.