git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Goo GGooo <googgooo@gmail.com>,
	linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: 2.6.17-rc6-mm2
Date: Fri, 16 Jun 2006 13:56:29 -0700	[thread overview]
Message-ID: <44931AFD.4070809@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606152335130.5498@g5.osdl.org>

Linus Torvalds wrote:
> 
> Actually, the really irritating thing is that we actually generate all 
> these nice status updates, which just makes pulling and cloning a lot more 
> comfortable, because you actually see what is going on, and what to 
> expect. 
> 
> Except they only work over ssh, where we have a separate channel (for 
> stderr), and with the native git protocol all that nice status work just 
> gets flushed to /dev/null :(
> 
> Dang. It's literally the most irritating part of the thing: the protocol 
> itself is exactly the same whether you go over ssh:// or over git://, but 
> that visual information about what is going on is missing, and it's 
> surprisingly important from a usability standpoint.
> 

Perhaps we shouldn't rely on stderr, and instead have a backchannel as part of the 
protocol itself.  After all, the protocol already does packetization, so all it needs is a 
reliable way to pick out the error/status packets; we could even combine that with a 
machine-readable code (like SMTP et al) that could get interpreted by the other side as 
needed.

	-hpa

  reply	other threads:[~2006-06-16 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ef5305790606142040r5912ce58kf9f889c3d61b2cc0@mail.gmail.com>
2006-06-16  1:14 ` 2.6.17-rc6-mm2 Goo GGooo
2006-06-16  2:46   ` 2.6.17-rc6-mm2 Linus Torvalds
2006-06-16  5:49     ` 2.6.17-rc6-mm2 Goo GGooo
2006-06-16  6:39       ` 2.6.17-rc6-mm2 Linus Torvalds
2006-06-16 20:56         ` H. Peter Anvin [this message]
2006-06-16 22:52           ` 2.6.17-rc6-mm2 Junio C Hamano
2006-06-17  0:22           ` 2.6.17-rc6-mm2 Linus Torvalds
2006-06-16 22:44         ` 2.6.17-rc6-mm2 bert hubert
2006-06-20  3:01         ` 2.6.17-rc6-mm2 Michal Ludvig
2006-06-20  3:22           ` 2.6.17-rc6-mm2 Linus Torvalds
2006-06-16 12:40       ` 2.6.17-rc6-mm2 Uwe Zeisberger

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=44931AFD.4070809@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=googgooo@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).