From: Johannes Sixt <j.sixt@viscovery.net>
To: Pete Wyckoff <pw@padd.com>
Cc: git@vger.kernel.org
Subject: Re: refs/replace advice
Date: Fri, 29 Jul 2011 17:49:53 +0200 [thread overview]
Message-ID: <4E32D6A1.8020304@viscovery.net> (raw)
In-Reply-To: <20110729153122.GA4535@padd.com>
Am 7/29/2011 17:31, schrieb Pete Wyckoff:
> I'm trying to use "git replace" to avoid cloning the entire set
> of duplicate commits across a slow inter-site link. Like this:
>
> ...---A----B----C site1/top
> \
> D---E---F site1/proj
>
> ...---A'---B'---C' site2/top
>
> It is true that "git diff C C'" is empty: they are identical.
...
> I thought maybe I could "git fetch --depth=N" where N would cover
> the range A'..site2/top, then replace. But testing with "git
> fetch --depth=3" still wants to fetch 100k objects.
On site2, don't you want to 'git fetch --depth=N site1' such that F down
to at least C (but not much more) is fetched, and then apply the graft or
replacement on site2?
-- Hannes
next prev parent reply other threads:[~2011-07-29 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 15:31 refs/replace advice Pete Wyckoff
2011-07-29 15:49 ` Johannes Sixt [this message]
2011-07-29 22:46 ` Pete Wyckoff
2011-08-02 21:54 ` Pete Wyckoff
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=4E32D6A1.8020304@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=pw@padd.com \
/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).