git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: refs/replace advice

From
PWPete Wyckoff <pw@padd.com>
Date
Aug 2, 2011, 21:54 UTC
Message-ID
<20110802215415.GA13327@arf.padd.com>
In-Reply-To
<20110729153122.GA4535@padd.com>
pw@padd.com wrote on Fri, 29 Jul 2011 08:31 -0700:
Show 8 quoted lines
> 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
Previous: Pete Wyckoff
Message 4 of 4 in “refs/replace advice”
  1. Pete WyckoffJul 29, 2011
  2. Johannes SixtJul 29, 2011
  3. Pete WyckoffJul 29, 2011
  4. Pete WyckoffAug 2, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.