Re: [PATCH] "git push": tellme-more protocol extension

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] "git push": tellme-more protocol extension

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:44:24

Jeff King [off-list ref] writes:
  2. This can actually be _more_ network intensive than your proposal.
I do not think this matters much in practice.  If you have tons of refs on
_your_ side to matter, some of them would be tags that are known to both
ends.  The only case it really is troublesome is when the sender does not
know _any_ of the refs the receiver presented to it.

In the illustration in the message you are responding to, if the commit A
was tagged at the shared repository when two developers cloned, it does
not matter if C is unknown to the second pusher.

So a potential improvement might be to ask for "tellme-more" only if we do
not know any of the refs the receiver showed us; my patch does it if there
is at least one unknown instead.

Re: [PATCH] "git push": tellme-more protocol extension

From: Jeff King <hidden>
Date: 2016-06-15 22:44:24

On Thu, Mar 20, 2008 at 09:24:18PM -0700, Junio C Hamano wrote:
So a potential improvement might be to ask for "tellme-more" only if we do
not know any of the refs the receiver showed us; my patch does it if there
is at least one unknown instead.
You can still get cases where doing this is more expensive than your
patch, because A..B is very small but shared_tag..A is very large. I'm
not sure which is more likely in practice.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help