From: Junio C Hamano <gitster@pobox•com>
To: Josef Wolf <jw@raven•inka.de>
Cc: git@vger•kernel.org
Subject: Re: Re-Transmission of blobs?
Date: Wed, 11 Sep 2013 10:14:54 -0700 [thread overview]
Message-ID: <xmqqsixbth4h.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20130911112758.GB14259@raven.wolf.lan> (Josef Wolf's message of "Wed, 11 Sep 2013 13:27:58 +0200")
Josef Wolf <jw@raven•inka.de> writes:
> On Di, Sep 10, 2013 at 10:51:02 -0700, Junio C Hamano wrote:
>> Consider this simple history with only a handful of commits (as
>> usual, time flows from left to right):
>>
>> E
>> /
>> A---B---C---D
>>
>> where D is at the tip of the sending side, E is at the tip of the
>> receiving side. The exchange goes roughly like this:
>>
>> (receiving side): what do you have?
>>
>> (sending side): my tip is at D.
>>
>> (receiving side): D? I've never heard of it --- please give it
>> to me. I have E.
>
> At this point, why would the receiving side not tell all the heads it knows
> about?
It did. The receiving end had only one branch whose tip is E. It
may have a tracking branch that knows where the tip of the sending
end used to be when it forked (which is C), so the above may say "I
have E and C". It actually would say "I have B and A and ..." for a
bounded number of commits, but that does not fundamentally change
the picture---the important point is it is bounded and there is a
horizon.
>> There are some work being done to optimize this further using
>> various techniques, but they are not ready yet.
And this still stands.
next prev parent reply other threads:[~2013-09-11 17:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 13:08 Re-Transmission of blobs? Josef Wolf
2013-09-10 17:51 ` Junio C Hamano
2013-09-11 11:27 ` Josef Wolf
2013-09-11 17:14 ` Junio C Hamano [this message]
2013-09-12 7:42 ` Josef Wolf
2013-09-12 9:23 ` Jeff King
2013-09-12 10:35 ` Josef Wolf
2013-09-12 19:44 ` Jeff King
2013-09-13 10:09 ` Josef Wolf
2013-09-16 21:55 ` Jeff King
2013-09-20 9:27 ` Josef Wolf
2013-09-24 7:36 ` Jeff King
2013-09-24 20:36 ` Josef Wolf
2013-09-12 12:45 ` Pyeron, Jason J CTR (US)
2013-09-12 19:56 ` Jeff King
2013-09-12 20:06 ` Pyeron, Jason J CTR (US)
2013-09-13 10:23 ` Josef Wolf
2013-09-13 11:51 ` Jason Pyeron
2013-09-13 12:16 ` Duy Nguyen
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=xmqqsixbth4h.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jw@raven$(echo .)inka.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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