[英]SVN2GIT - no associated commit metadata from SVN, skipping
I am getting warning "no associated commit metadata from SVN, skipping" 我收到警告“ SVN没有关联的提交元数据,正在跳过”
I am using https://github.com/nirvdrum/svn2git tool. 我正在使用https://github.com/nirvdrum/svn2git工具。 What does the above message mean?
以上消息是什么意思? I am trying to migrate whole history from svn to git.
我正在尝试将整个历史记录从svn迁移到git。
I'm not sure what that warning means, but I'd recommend not using that tool. 我不确定该警告的含义,但建议您不要使用该工具。
For a one-time migration git-svn
is not the right tool for conversions of repositories or parts of repositories. 对于一次性迁移,
git-svn
不是转换存储库或部分存储库的正确工具。 It is a great tool if you want to use Git as frontend for an existing SVN server, but for one-time conversions you should not use git-svn
, but svn2git
which is much more suited for this use-case. 这是一个伟大的工具,如果你想使用Git的作为前端为现有的SVN服务器,但对于一次性转换,你不应该使用
git-svn
,但svn2git
这是该用例更加适合。
There are plenty tools called svn2git
, the probably best one is the KDE one from https://github.com/svn-all-fast-export/svn2git . 有很多名为
svn2git
工具,最好的一种可能是来自https://github.com/svn-all-fast-export/svn2git的KDE工具。 I strongly recommend using that svn2git
tool. 我强烈建议您使用该
svn2git
工具。 It is the best I know available out there and it is very flexible in what you can do with its rules files. 这是我所知道的最好的,它可以很灵活地处理其规则文件。
The nirvdrum svn2git
one you use effectively calls git-svn
and then does some post-processing to overcome some of the drawbacks of git-svn
, but it still suffers from quite some of them. 您有效使用的nirvdrum
svn2git
称为git-svn
,然后进行一些后期处理以克服git-svn
某些缺点,但是它仍然遭受许多缺点。
You will be easily able to configure svn2git
s rule file to produce the result you want from your current SVN layout, including any complex histories like yours that might exist and including producing several Git repos out of one SVN repo or combining different SVN repos into one Git repo cleanly in one run if you like. 您将能够轻松配置
svn2git
的规则文件,以从当前的SVN布局中生成所需的结果,包括可能存在的任何类似您的复杂历史记录,以及从一个SVN存储库中生成多个Git存储库,或将不同的SVN存储库合并为一个如果愿意,可以一站式干净地完成Git回购。
If you are not 100% about the history of your repository, svneverever
from http://blog.hartwork.org/?p=763 is a great tool to investigate the history of an SVN repository when migrating it to Git. 如果您不是100%知道存储库的历史记录,请从http://blog.hartwork.org/?p=763中
svneverever
,这是在将SVN存储库迁移到Git时调查其历史记录的绝佳工具。
Even though git-svn
or the nirvdrum svn2git
is easier to start with, here are some further reasons why using the KDE svn2git
instead of git-svn
is superior, besides its flexibility: 尽管
git-svn
或nirvdrum svn2git
较容易svn2git
,但还有一些其他原因为什么除了灵活性之外,使用KDE svn2git
而不是git-svn
更胜一筹:
svn2git
(if the correct one is used), this is especially the case for more complex histories with branches and merges and so on svn2git
(如果使用了正确的历史记录)可以更好,更干净地重建历史记录,对于具有分支和合并等更复杂历史记录的情况尤其如此 git-svn
the tags contain an extra empty commit which also makes them not part of the branches, so a normal fetch
will not get them until you give --tags
to the command as by default only tags pointing to fetched branches are fetched also. git-svn
标签会包含一个额外的空提交,这也会使它们不成为分支的一部分,因此,除非您将--tags
交给命令, --tags
正常的fetch
将不会获取它们,因为默认情况下,还会仅获取指向获取的分支的标签。 With the proper svn2git tags are where they belong svn2git
, with git-svn
you will loose history eventually svn2git
配置,而使用git-svn
最终会丢失历史记录 svn2git
you can also split one SVN repository into multiple Git repositories easily svn2git
您还可以轻松地将一个SVN存储库拆分为多个Git存储库 svn2git
than with git-svn
svn2git
比git-svn
快svn2git
倍 You see, there are many reasons why git-svn
is worse and the KDE svn2git
is superior. 您会看到
git-svn
较差而KDE svn2git
较差的原因很多。 :-) :-)
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.