From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Fixup no-progress for fetch & clone
Date: Sat, 24 Feb 2007 18:56:29 +0100 [thread overview]
Message-ID: <erpu4b$daa$1@sea.gmane.org> (raw)
In-Reply-To: alpine.LRH.0.82.0702240922250.29426@xanadu.home
Nicolas Pitre wrote:
> On Sat, 24 Feb 2007, Junio C Hamano wrote:
>
>> Nicolas Pitre <nico@cam.org> writes:
>>
>>> How does that solve the issue with servers (currently all of them) that
>>> don't know about the new sideband?
>>
>> I actually happen to consider that a non problem.
>>
>> It is true that you can only prepare the client and server side
>> by 1.5.1, and new clients talking to 1.5.0 or older servers
>> would not be able to squelch the noise. But that is _not_ a new
>> problem anyway, and given time the server side will eventually
>> be updated to 1.5.1 or later. If anything else, it would give
>> incentive to people to upgrade their servers to 1.5.1 ;-)
>
> Well... for such a special case feature I doubt this might be such a
> great insentive. And since locally filtering on '\r' is so simple I
> wonder what the complexity of the alternative solution really buys us.
Slighly less bandwidth used (we don't send progress report)?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-02-24 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 19:03 [PATCH] Fixup no-progress for fetch & clone Johannes Schindelin
2007-02-23 20:08 ` Junio C Hamano
2007-02-24 1:19 ` Johannes Schindelin
2007-02-24 1:29 ` Junio C Hamano
2007-02-24 1:47 ` Johannes Schindelin
2007-02-24 1:48 ` Nicolas Pitre
2007-02-24 2:14 ` Junio C Hamano
2007-02-24 2:15 ` Johannes Schindelin
2007-02-24 2:28 ` Nicolas Pitre
2007-02-24 2:37 ` Johannes Schindelin
2007-02-24 2:47 ` Nicolas Pitre
2007-02-24 4:58 ` Junio C Hamano
2007-02-24 5:14 ` Nicolas Pitre
2007-02-24 8:14 ` Junio C Hamano
2007-02-24 14:27 ` Nicolas Pitre
2007-02-24 17:56 ` Jakub Narebski [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='erpu4b$daa$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).