在迁移到git(git-svn)时排除已删除的svn分支/标签 [英] Exclude deleted svn branches/tags on migration to git (git-svn)

问题描述

我目前正在将一个历史悠久的大型存储库从SVN迁移到git. svn存储库具有许多分支和标签.我已经从SVN存储库中清理了很多文件，但是当我使用git svn clone命令时，它也会克隆所有已删除的分支和标签.

I'm currently migrating a huge repository with a long history from SVN to git. The svn repository has many branches and tags. I've cleaned up a lot of them from the SVN repo, but when I use the git svn clone command, it clone all the deleted branches and tags as well.

问题是，是否存在一种有效且简便的方法(简单命令)来排除使用git svn或svn2git(或与此相关的任何其他工具)获取已删除的分支和标记的情况?

Question is, is there an efficient and easy way (simple command) to exclude fetching deleted branches and tags with git svn or svn2git (or any other tool for that matter)?

推荐答案

TL; DR:是的，如果您使用正确的svn2git工具

TL;DR: Yes, if you use the right svn2git tool

对于一次性迁移，git-svn不是用于转换存储库或存储库部分的正确工具.如果要将Git用作现有SVN服务器的前端，这是一个很好的工具，但是对于一次性转换，您应该不使用git-svn，但是svn2git更适合这个用例.

For a one-time migration git-svn is not the right tool for conversions of repositories or parts of a repository. 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.

有很多名为svn2git的工具，可能最好的工具是来自 https://github.com/svn-all-fast-export/svn2git .我强烈建议使用该svn2git工具.这是我所知道的最好的，它在处理规则文件方面非常灵活.

There are plenty tools called svn2git, the probably best one is the KDE one from https://github.com/svn-all-fast-export/svn2git. I strongly recommend using that svn2git tool. It is the best I know available out there and it is very flexible in what you can do with its rules files.

您将能够轻松配置svn2git规则文件，以从当前SVN布局中生成所需的结果，包括可能存在的任何复杂历史记录，以及从一个SVN存储库中生成多个Git存储库，或组合使用不同的SVN如果愿意，可以一次性将一个仓库完整地存储到一个Git仓库中，并且排除不迁移的任何路径，分支或标签，尽管如果有人丢弃了宝贵的代码历史记录，我总是会哭泣.

You will be easily able to configure svn2gits rule file to produce the result you want from your current SVN layout, including any complex histories 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 and also excluding any paths or branches or tags you don't to have migrated, though I'm always crying a little if someone discards code history which is precious.

如果您不是100％了解存储库的历史记录，请从 http://blog.hartwork.org/?p=763 是将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.

尽管git-svn或小军鼓svn2git较容易入门，但还有一些其他原因为什么除了灵活性之外，使用KDE svn2git代替git-svn更为优越:

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:

• 通过svn2git(如果使用了正确的历史记录)，可以更好地重建历史记录，并且更整洁(对于使用分支和合并等更复杂的历史记录，尤其如此)
• 标签是真实标签，不是Git中的分支
• 带有git-svn的标记包含一个额外的空提交，这也使它们不属于分支，因此普通的fetch不会得到它们，直到您将--tags赋予命令为止，因为默认情况下仅指向提取的分支也将被提取.带有正确的svn2git标签是它们所属的地方
• 如果您在SVN中更改了布局，则可以轻松地使用svn2git进行配置，而使用git-svn最终会丢失历史记录
• 使用svn2git，您还可以轻松地将一个SVN存储库拆分为多个Git存储库
• 或将同一SVN根目录中的多个SVN存储库轻松组合到一个Git存储库中
• 正确的svn2git转换要比git-svn快上万亿次.

• the history is rebuilt much better and cleaner by svn2git (if the correct one is used), this is especially the case for more complex histories with branches and merges and so on
• the tags are real tags and not branches in Git
• with 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. With the proper svn2git tags are where they belong
• if you changed layout in SVN you can easily configure this with svn2git, with git-svn you will loose history eventually
• with svn2git you can also split one SVN repository into multiple Git repositories easily
• or combine multiple SVN repositories in the same SVN root into one Git repository easily
• the conversion is a gazillion times faster with the correct svn2git than with git-svn

您看到，git-svn较差而KDE svn2git较优的原因很多. :-)

You see, there are many reasons why git-svn is worse and the KDE svn2git is superior. :-)

这篇关于在迁移到git(git-svn)时排除已删除的svn分支/标签的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！