I have recently started a new project that has begun its life as a fork of an old project, then heavily modified. At the same time I am looking into migrating from svn to git. Since this is a separate project, I thought I should split it into a separate git repository and keep them separate going forward, however, since they have common ancestry up to this point, I would like to make sure that all of that data is not duplicated. I thought what I could do is set up an initial repository that is fully packed and use it as a read only archive to contain all of the shared history, then clone that into two new repositories for the two separate projects. It seems like I can do this by running a clone -s so that the archive is set up to be an alternate object store, then its big pack file will be found and used for all of the old history, but new commits will be specific to each of the two new respective projects. The problem I run into though, is when it comes time to repack the new projects. If I run a repack -a, then the new project has everything copied out of the archive and into its new main pack, rather than continuing to use the archive repository for old history, and just pack everything since then. I guess I am looking for is somewhere between a full repack and an incremental; a way to make repack -a discard existing local packs, but to respect the alternate packs and omit objects they contain from the new local pack. Is this possible? -- 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