From: Junio C Hamano <gitster@pobox.com>
To: Brad Litterell <brad@evidence.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Question about how git determines the minimum packfile for a push.
Date: Sun, 26 Apr 2015 21:39:32 -0700 [thread overview]
Message-ID: <CAPc5daV2GmtaknNhrBc7ofMZPsKPUn81SHBVPNdHHTXJs8ubdQ@mail.gmail.com> (raw)
In-Reply-To: <E51394554A503C4E852F9BEE46B03E8D01E4E784@TI-ODIN.tasernet.com>
On Sun, Apr 26, 2015 at 5:41 PM, Brad Litterell <brad@evidence.com> wrote:
>
> Is it possible git is not computing the delta correctly?
> Or does git only look at the top-level commit objects to figure out what to
> include in the push packfile?
We walk the commit graph backwards to discover the common ancestries to
minimize the network cost when fetching, but I do not think the
reverse direction
has such smart in the protocol.
If you fetch (not "pull") first to remote tracking branches and then push, that
probably will reduce the transfer, as the side that pushes is the only one that
decides what objects are sent in "git push -> git receive-pack" direction.
next prev parent reply other threads:[~2015-04-27 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 0:41 Question about how git determines the minimum packfile for a push Brad Litterell
2015-04-27 4:39 ` Junio C Hamano [this message]
2015-04-28 5:33 ` Jeff King
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=CAPc5daV2GmtaknNhrBc7ofMZPsKPUn81SHBVPNdHHTXJs8ubdQ@mail.gmail.com \
--to=gitster@pobox.com \
--cc=brad@evidence.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).