blocks|key|1338847|text|cvs2svn有一个cvs2git模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1338848|entityMap|0|LINK|mutability|MUTABLE|url|http://cvs2svn.tigris.org/cvs2git.html^0|A|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

cvs2svn has a <a href="http://cvs2svn.tigris.org/cvs2git.html" rel="noreferrer">cvs2git</a> mode.

blocks|key|1338977|text|如果任何人仍然不习惯使用CVS，你可以尝试“垃圾”：https://github.com/rcls/crap它很快(只要访问CVS是快速的)，支持你在cvs+repos中发现的乱七八糟的东西，而且是增量的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1338978|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/rcls/crap^0|Q|S|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If anyone still has the misfortune of using CVS, you could try "crap" : <a href="https://github.com/rcls/crap">https://github.com/rcls/crap</a>
It's fast (as far as accessing CVS can be fast), supports the messes that you find in cvs repos, and incremental.

blocks|key|1338900|text|另一种方法可能是使用git+cvsimport+*|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1338901|entityMap|0|LINK|mutability|MUTABLE|url|http://www.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html^0|A|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

An alternative might be to use <a href="http://www.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html" rel="noreferrer">git cvsimport *</a>

blocks|key|1338875|text|我自己还没有试过，但朋友们报告说，首先从CVS转换到SVN，然后从SVN转换到Git，都很成功。似乎完成这些转换的工具比直接从CVS到Git的转换更彻底。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338876|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I've not tried this myself, but friends have reported good success converting first from CVS to SVN, and then from SVN to Git. It seems that the tools to do those respective transitions have been more thoroughly shaken out than a direct CVS to Git transition.

blocks|key|1338946|text|我试过cvs2git，git-cvsimport和parsecvs。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1338947|cvs2git有时(据我所知)会为标签创建假分支。|1338948|git-cvsimport不支持变更集使用多个标签。但是，可以为cvsps获取一些额外的更改以支持它，并将原始的git-cvsimport更改为使用更新的cvsps的内容(我已经尝试过了，似乎可以工作)。在优点方面，它支持增量更新，并具有适当导入合并的逻辑(但它需要适当的提交消息格式)。|1338949|到目前为止，parsecvs给了我最好的结果。不幸的是，web上可用的代码不能用最新的git干净地编译。这种改变虽然不是微不足道的，但却是可行的。|1338950|编辑:看起来ESR同时接管了cvsps和parsecvs，所以CVS->GIT迁移还有一些希望。但他已经在一些邮件列表中提到，他可能会宣布他最近接管的一些工具正式死亡。|offset|length|1338951|entityMap|0|LINK|mutability|MUTABLE|url|http://www.catb.org/~esr/|1|http://gitorious.org/cvsps/cvsps|2|https://github.com/BartMassey/parsecvs^0|0|0|0|0|6|3|0|E|5|1|K|8|2|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@$J|12|K|13|1|14]|$J|15|K|16|1|17]|$J|18|K|19|1|1A]]|A|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]|T|$5|O|P|Q|A|$R|U]]|V|$5|O|P|Q|A|$R|W]]]]

I've tried cvs2git, git-cvsimport and parsecvs.

cvs2git sometimes (as far as I remember) creates bogus branches for tags.

git-cvsimport does not support multiple tags for a changeset. It is possible however to grab some additional changes for cvsps to support it and change the original git-cvsimport to something which uses updated cvsps (I've tried it and it seems to work). On the advantage side it supports incremental updates and has some logic to properly import merges (but it REQUIRES appropriate format for commit message).

parsecvs so far gave me the best results. Unfortunately the code available on the web does not compile cleanly with the latest git. The change while not trivial is doable.

EDIT: It looks like <a href="http://www.catb.org/~esr/" rel="nofollow">ESR</a> took over both <a href="http://gitorious.org/cvsps/cvsps" rel="nofollow">cvsps</a> and <a href="https://github.com/BartMassey/parsecvs" rel="nofollow">parsecvs</a> so there is some hope for CVS->GIT migration. BUT he already mentioned on some mailing list that he may declare some of the tools he took over recently officially dead.

blocks|key|1339004|text|我读了Vanuan和mhagger对它的评论的答案。不幸的是，mhagger没有发布如何使用cvs2git做到这一点。这里写得很好：http://www.mcs.anl.gov/~jacob/cvs2svn/cvs2git.html|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1339005|我使用cvs2git而不是git-cvsimport，因为git-cvsimport的文档建议使用它来避免git-cvsimport的问题：https://www.kernel.org/pub/software/scm/git/docs/git-cvsimport.html#issues|1339006|我从Debian+Sid上的sourceforge+CVS存储库创建了一个git存储库，它遵循了它的精髓：|1339007|$+apt-get+install+cvs2svn+cvs
$+mkdir+project.cvs
$+rsync+-av+rsync://${PROJECT}.cvs.sourceforge.net/cvsroot/${PROJECT}/+project.cvs
$+cvs2git+--blobfile=git-blob.dat+--dumpfile=git-dump.dat+--username=cvs2git+project.cvs
$+mkdir+project.git
$+cd+project.git
$+git+init
$+cat+../git-blob.dat+../git-dump.dat+%7C+git+fast-import|code-block|syntax|javascript|1339008|因为cvs2git需要访问整个历史记录，所以需要rsync步骤。简单的结账是不够的。|1339009|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mcs.anl.gov/~jacob/cvs2svn/cvs2git.html|1|https://www.kernel.org/pub/software/scm/git/docs/git-cvsimport.html#issues^0|1A|7|1U|1E|0|0|3|7|D|D|T|D|1H|D|1Y|22|1|0|0|0|2|7|O|5|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]]|E|$]]|$1|F|3|G|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|H|3|I|5|6|7|1I|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1J|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1P|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]|Y|$5|T|U|V|E|$W|Z]]]]

I read the answer by Vanuan and mhagger's comments to it. Unfortunately mhagger didn't post how to do it with <code>cvs2git</code>. It is all very well written up here: <a href="http://www.mcs.anl.gov/~jacob/cvs2svn/cvs2git.html" rel="nofollow">http://www.mcs.anl.gov/~jacob/cvs2svn/cvs2git.html</a>

I used <code>cvs2git</code> instead of <code>git-cvsimport</code> because the documentation of <code>git-cvsimport</code> suggests to use it instead to avoid the problems of <code>git-cvsimport</code>: <a href="https://www.kernel.org/pub/software/scm/git/docs/git-cvsimport.html#issues" rel="nofollow">https://www.kernel.org/pub/software/scm/git/docs/git-cvsimport.html#issues</a>

It follows essence of it that worked for me to create a git repository from a sourceforge CVS repository on Debian Sid:

<pre><code>$ apt-get install cvs2svn cvs
$ mkdir project.cvs
$ rsync -av rsync://${PROJECT}.cvs.sourceforge.net/cvsroot/${PROJECT}/ project.cvs
$ cvs2git --blobfile=git-blob.dat --dumpfile=git-dump.dat --username=cvs2git project.cvs
$ mkdir project.git
$ cd project.git
$ git init
$ cat ../git-blob.dat ../git-dump.dat | git fast-import
</code></pre>

The <code>rsync</code> step is needed because <code>cvs2git</code> needs access to the whole history. A simple checkout is not enough.

blocks|key|1339071|text|我是cvs-fast-export的维护者。我曾经维护过cvs和parse2cvs，并仔细评估过cvs-fastimport和cvs2git。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1339072|从CVS到git的转换是一个棘手的问题，在可阻挡的边缘情况下。所有现有的转换工具都有已知的局限性，其中一些非常严重。|1339073|我建议先尝试使用cvs-fast-export。它比其他任何东西都能产生更好、更快的转换，除非在极少数情况下它完全失败并跳出困境。如果你遇到了罕见但可怕的“分支周期错误”，可以试试cvs2git。|1339074|不要相信cvs-fastimport，它有很多buggy，而且经常搞砸分支连接。|1339075|有关更多信息，请参阅http://www.catb.org/esr/cvs-fast-export/|offset|length|1339076|entityMap|0|LINK|mutability|MUTABLE|url|http://www.catb.org/esr/cvs-fast-export/^0|0|0|0|0|A|14|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$J|Y|K|Z|1|10]]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

I'm the maintainer of cvs-fast-export. I used to maintain cvsps and parse2cvs and have closely evaluated cvs-fastimport and cvs2git.

CVS to git conversion is a hard, nasty problem with rebarbative edge cases. All the existing conversion tools have known limitations, some quite serious.

I recommend trying cvs-fast-export first. It produces better, faster conversions than anything else, except in rare cases where it fails cleanly and bails out. If you get the rare but dreaded "branch cycle error", try cvs2git.

Do not trust cvs-fastimport, it is quite buggy and often screws up branch joins.

For more, see <a href="http://www.catb.org/esr/cvs-fast-export/" rel="nofollow noreferrer">http://www.catb.org/esr/cvs-fast-export/</a>

blocks|key|1554563|text|您可以将fromcvs添加到列表中。它的转换效果很好，而且非常快，而且是增量式的。然而，它不做粘性标签，只做分支。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1554564|entityMap|0|LINK|mutability|MUTABLE|url|http://ww2.fs.ei.tum.de/~corecode/hg/fromcvs^0|4|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You can add <a href="http://ww2.fs.ei.tum.de/~corecode/hg/fromcvs" rel="nofollow noreferrer">fromcvs</a> to the list. It converts well and is extremely fast and also incremental. It does not do sticky tags, only branches, however.

blocks|key|1339036|text|我发现cvs-fast-export做得很好。我不得不自己下载并编译它，但这样做没有任何重大问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1339037|entityMap|0|LINK|mutability|MUTABLE|url|https://gitlab.com/esr/cvs-fast-export^0|3|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I found <a href="https://gitlab.com/esr/cvs-fast-export" rel="nofollow">cvs-fast-export</a> did an excellent job. I had to download and compile it myself, but didn't have any significant issues doing so.

I intend to switch over from CVS to Git. 
In the case of SVN, there seems to be <code>cvs2svn</code>. Is there a similar tool to easily migrate from CVS to Git?

Is there a migration tool from CVS to Git?

我打算从CVS切换到Git。在SVN的情况下，似乎有cvs2svn。有没有类似的工具可以很容易地从CVS迁移到Git？

问有没有从CVS到Git的迁移工具？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有从CVS到Git的迁移工具？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有从CVS到Git的迁移工具？
EN