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 -- 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