Git cvsimport 的加速和注意事项？
我们正在尝试从 cvs 迁移到 git。
我们的目标是 1）完善当前代码库 2）可用历史记录。如果旧分支中缺少条目，我们也不太关心。
两条评论：
即使使用 cvs 存储库的本地副本，也需要很长时间。试运行花费了 24 多个小时（7.5 GB cvs 代码库；P4 2.0 ghz 机器、2 GB RAM、10K 驱动器。Git 将其压缩到 1.8 GB）。因为 CVS 本身占用了 99% 的 cpu，所以我想它是 cpu 限制的。有什么办法可以加快速度吗？
标准输出有很多警告。哪些重要？哪些没有？
警告：无效的 PatchSet 5763，标签 pre-merge-pe-2-3-merge-26： conf/peTEST.conf:1.4=之后，src/java/com/participate/util/XSLUtilTEST.java:1.1=之前。被视为“之前” 文件 returned/workflow/xml/bpd.xml 的修订版 1.167.2.11 已标记但不存在 文件 returned/workflow/xml/bpd.xml 的修订版 1.106 已标记但不存在 分支 PE-2-3 已经存在！ 警告：提交消息不符合 UTF-8。
提前
致谢
we're trying our hand at migrating from cvs to git.
Our goals are
1) perfect current codebase
2) usable history. 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. 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). Because CVS itself takes up 99% of the cpu, I imagine it's cpu bound. Any way to speed it up?
Stdout has a bunch of warnings. 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
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
“git cvsimport”有许多已知的错误 并且不应被视为从 CVS 转换为 git 的可靠方法。我推荐 cvs2svn （特别是它的 cvs2git 模式），它非常灵活，将保留您的所有 CVS 历史记录。我会使用 cvs2svn 的主干版本，因为它与最新发布的版本（2.3.0）相比有很多改进。
"git cvsimport" has many known bugs and should not be considered a reliable means of converting from CVS to git. I recommend cvs2svn (in particular its cvs2git mode), which is very flexible and will preserve all of your CVS history. I would use the trunk version of cvs2svn, as it has many improvements compared to the latest released version (2.3.0).