On 3/28/08, Alex Bennee <kernel-hacker@bennee.com> wrote:
quoted text
>  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).

You used git-repack and git-gc, right?  If not, the repo will be
bigger than it should be.

quoted text
>  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.

"git show-branch -a" probably does what you want.

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

You probably want to look at git-filter-branch, particularly the
--parent-filter option.

Note that 2(a) would be easiest if you just did it before importing
from CVS at all, since it's easy to remove old modules from CVS just
by moving the files out of the way.

Have fun,

Avery
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html