From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Make fetch-pack play nicer with servers which do not speak multi_ack
Date: Tue, 25 Oct 2005 11:56:01 -0700 [thread overview]
Message-ID: <7vll0he88u.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: Pine.LNX.4.63.0510251104470.24174@wbgn013.biozentrum.uni-wuerzburg.de
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 1139 bytes --]
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> But you are right. If you made 20 commits on top of my "master"
>> branch head, we should send those 20 (and the commit you based
>> on your changes, which the other end has), way before sending
>> the ancient v0.99 tag. Probably, we should never be sending
>> v0.99 tag as "have" if we are going to send your "master" branch
>> head, since the commit that tag refers to is reachable by your
>> "master" branch head but there are a lot more commit between
>> them, some of which will give us better "common" selected, and
>> that v0.99 tag is what the other end said they have so is known
>> to be ACKed if sent.
>
> You^[.A^[N4re right. Complete common refs are sent even if they are ancestors of
> other complete common refs. I^[.A^[N4ll think about that.
I just realized that I have two refs you would rather send the
last while fetching from me most of the time: junio-gpg-pub tag
and todo head. If you manage to get acked either by non multi
aware remote before saying "have" on anything on the main
branch, I think you would get *everything* back --- which is
quite bad.
next prev parent reply other threads:[~2005-10-25 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 6:59 [PATCH] Make fetch-pack play nicer with servers which do not speak multi_ack Johannes Schindelin
2005-10-25 8:30 ` Junio C Hamano
2005-10-25 9:51 ` Johannes Schindelin
2005-10-25 18:56 ` Junio C Hamano [this message]
2005-10-25 23:32 ` Junio C Hamano
2005-10-25 23:53 ` Johannes Schindelin
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=7vll0he88u.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--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