Hi, I've succeeded in porting our whole CVS repository into git (with plenty of swap, cvsps is very memory hungry). Now we have a reference historical repository I need to think about creating one we actually use for day to day use (the .git is currently in the order of 650Mb which is a little heavy for pushing around DSL links willy nilly). What I need to achieve is fairly simple. 1. Find the common ancestor point for all the product branches I want to keep in the repo. Can anyone point me to the magic invocation that would allow this? git-merge-base can find the common point for two commits, do I just have to iteratively use that? I'm currently working over a terminal link so it would be dead handy if there was a visual way of showing what gitk --all does on the command line. 2. Create a new repo, starting at the common ancestor point 2(a). I'd need to remove the orphaned old CVS modules which are still around but not referenced any more. 3. Create the product branches and import ANCESTOR..BRANCH_HEAD into them I'm not sure if I could pull directly into the new repo here. I could do it by doing a: old_repo: git-format-patch ANCESTOR..BRANCH_HEAD new_repo: git-am ../old_repo/0* But I'm open to newer cleaner ways of dealing with this. Has anyone done this before? Are there cleaner ways of dealing with this? -- Alex, homepage: http://www.bennee.com/~alex/ When one knows women one pities men, but when one studies men, one excuses women. -- Horne Tooke -- 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
