From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>,
Shawn Pearce <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Is anyone working on a next-gen Git protocol (Re: [PATCH v3 0/8] Hiding refs)
Date: Tue, 05 Feb 2013 08:03:11 -0800 [thread overview]
Message-ID: <7vfw1avjcw.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACBZZX7G=V9L+zEA2MQFjQW8tRA0i1Gk3nUYdg5dDy35v74SEw@mail.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Tue, 5 Feb 2013 12:14:32 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> Do you have any plans for something that *does* have the reduction of
> network bandwidth as a primary goal?
Uncluttering gives reduction of bandwidth anyway, so I do not see
much point in the distinction you seem to be making.
> Is this what you've been working on? Because if so I misunderstood you
> thinking you were going to work on something that gave clients the
> ability specify what they wanted before the initial ref advertisement.
> ...
> 4. http://thread.gmane.org/gmane.comp.version-control.git/207190
"Who speaks first" mentioned in 4. above, was primarily about
"delaying ref advertisement", which would be a larger protocol
change. Nobody seems to have attacked it since it was discussed,
and I was tired of hearing nothing but complaints and whines. This
"hiding refs" series was done as a cheaper way to solve a related
issue, without having to wait for the solution of "delaying
advertisement", which is an orthogonal issue.
next prev parent reply other threads:[~2013-02-05 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 11:14 Is anyone working on a next-gen Git protocol (Re: [PATCH v3 0/8] Hiding refs) Ævar Arnfjörð Bjarmason
2013-02-05 16:03 ` Junio C Hamano [this message]
2013-02-05 20:07 ` Ævar Arnfjörð Bjarmason
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=7vfw1avjcw.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.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