pw@xxxxxxxx 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html