简体繁体 English

Git cvsimport的加速和警告？

[英]Speedup and Caveats with Git cvsimport?

原文 2010-09-08 16:35:11 7 1 git/ git-cvs

we're trying our hand at migrating from cvs to git. 我们正在尝试从cvs迁移到git。

Our goals are 1) perfect current codebase 2) usable history. 我们的目标是1）完善当前的代码库2）可用历史。 If it's missing an entry in an old branch, we don't care so much. 如果它缺少旧分支中的条目，则我们不在乎。

Two comments: 两条评论：

Even with a local copy of the cvs repository, it takes a very long time. 即使使用cvs信息库的本地副本，也要花费很长时间。 The dry run took over 24 hours (7.5 gb cvs codebase; P4 2.0 ghz machine, 2gb RAM, 10K drives. Git scrunched it down to 1.8 gb). 空运行耗时24小时（7.5 gb cvs代码库； P4 2.0 GHz机器，2 gb RAM，10K驱动器。Git将其压缩到1.8 gb）。 Because CVS itself takes up 99% of the cpu, I imagine it's cpu bound. 因为CVS本身占用了99％的cpu，所以我想它是cpu的约束。 Any way to speed it up? 有什么办法可以加快速度吗？
Stdout has a bunch of warnings. Stdout有很多警告。 Which ones matter? 哪个重要？ Which ones don't? 哪个不？

WARNING: Invalid PatchSet 5763, Tag pre-merge-pe-2-3-merge-26: conf/peTEST.conf:1.4=after, src/java/com/participate/util/XSLUtilTEST.java:1.1=before. Treated as 'before' revision 1.167.2.11 of file derived/workflow/xml/bpd.xml is tagged but not present revision 1.106 of file derived/workflow/xml/bpd.xml is tagged but not present Branch PE-2-3 already exists! Warning: commit message does not conform to UTF-8.

thanks in advance 提前致谢

will 将

1 个解决方案

"git cvsimport" has many known bugs and should not be considered a reliable means of converting from CVS to git. “ git cvsimport”具有许多已知的错误，因此不应被视为从CVS转换为git的可靠方法。 I recommend cvs2svn (in particular its cvs2git mode ), which is very flexible and will preserve all of your CVS history. 我建议使用cvs2svn （尤其是其cvs2git模式），它非常灵活，可以保留所有 CVS历史记录。 I would use the trunk version of cvs2svn, as it has many improvements compared to the latest released version (2.3.0). 我将使用cvs2svn的主干版本，因为与最新发布的版本（2.3.0）相比，它具有许多改进。