From: Pete Wyckoff <pw@padd.com>
To: git@vger.kernel.org
Cc: Johannes Sixt <j.sixt@viscovery.net>
Subject: Re: refs/replace advice
Date: Tue, 2 Aug 2011 17:54:15 -0400 [thread overview]
Message-ID: <20110802215415.GA13327@arf.padd.com> (raw)
In-Reply-To: <20110729153122.GA4535@padd.com>
pw@padd.com wrote on Fri, 29 Jul 2011 08:31 -0700:
> I've got two near-identical git repos, both imported from
> gigantic upstream p4 repos. They started at slightly different
> times so have different commit SHA1s, even though the tree
> contents are the same. I can't filter-branch either of them; too
> many users already.
>
> I'm trying to use "git replace" to avoid cloning the entire set
> of duplicate commits across a slow inter-site link. Like this:
To follow-up, I decided this was not the right approach.
Instead, for future git-p4 repo creation, I've patched git-p4
to make sure the timestamps and hence the initial SHA1s are
identical.
Thanks, Hannes, for your suggestion, though.
-- Pete
prev parent reply other threads:[~2011-08-02 21:54 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
2011-07-29 22:46 ` Pete Wyckoff
2011-08-02 21:54 ` Pete Wyckoff [this message]
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=20110802215415.GA13327@arf.padd.com \
--to=pw@padd.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.