On 10/16/06, Sam Vilain <sam@xxxxxxxxxx> wrote:
Jon Smirl wrote: > cvsps works ok on small amounts of data, but it can't handle the full > Mozilla repo. The current idea is to convert the full repo with > cvs2git and build the ini file needed by cvsps to support incremental > imports. After that use cvsps. > Looking through the client.mk used to check out the sub-portions of the CVS repository, I have to ask; Why are you trying to import this big collection of projects into a single git repository?
All of Mozilla is in a single CVS repo, client.mk is checking out directories from the mozilla project. This is how it has been historically for over ten years. It also allows commits that simultaneously go to all subcomponents when interfaces are changed. Even if it was split into different git repos you still need to download about 70% of them to build the browser. I've been trying to simply translate the existing repo without changing it's structure in any way. Changing structure is going to require a lot of buy-in from all of the developers.
View git's repositories not as a container for an entire community's code base, but more as object partitions. Currently you are quite happy to use per-file version control partitions inherent to CVS. Now you are looking at removing all of the partitions completely and hoping to end up with something managable. That it has been possible at all to fit it into the space less than the size of a CD is staggering, but surely a piecemeal approach would be a pragmatic solution to this problem. Sam.
-- Jon Smirl jonsmirl@xxxxxxxxx - 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