Chris Lee <clee@xxxxxxx> wrote: > Also, please note, the 3GB packed repo is only about 2/3 of the full > KDE repo - I cut off the import at revision 409202, because that was > when the KDE svn admins decided to move a bunch of modules from > /trunk/ to /trunk/KDE/ and it screws up everything. So a *full* KDE > history import would definitely be more than 4GB, packed. Hmm.. This movement from /trunk to /trunk/KDE could be a good case for the (still-improving) --follow-parent feature in git-svn. I've resigned to the fact that git-svn (and git) is not ideal for tracking the entire KDE repository. I don't think most (sane) developers check out the entire repository root when working on KDE, and cloning a 3GB pack just isn't realistic these days. But if splitting the monster repository into separate repositories is an option for KDE, and I can make --follow-parent do what it's supposed to do very well: then it could be a nice way to make things more manageable for developers that will eventually switch to. For tracking the trunk of kde-common, I'm running with my work-in-progress version of git-svn: git-svn init -i kde-common svn://anonsvn.kde.org/home/kde/trunk/KDE/kde-common git-svn fetch -i kde-common --follow-parent It seems to be following kde-common into pre-409202 revisions (down to r11472) pretty well. I'll upload the result to git.bogomips.org when I'm done. You can get my latest git-svn here: git://git.bogomips.org/git-svn Note: I've not used this to dcommit for serious work, so I can't tell if it's really useful. But fetching seems fine. The current --follow-parent implementation does not handle some cases very well. I would like to get it to correctly track parents analogous to the way gitk was merged into git, so that subprojects merged into a bigger project are currently ignored. Junio: there are some huge changes; so please don't merge it into master yet, I don't feel it's ready yet, but it should be sometime in the next week. I would like to see this in 1.5.0, but only if it's not horribly broken (especially w.r.t committing). -- Eric Wong - 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