从环绕声SCM导入Git？ [英] Git Import from Surround SCM?

问题描述

我的公司在Surround SCM中有一个大的代码库，它在几年前从SourceSafe迁移过来。我们正在寻找更适合我们需求的产品，但是将我们的历史从Surround发展出来是一项挑战。

使用git导入器搜索Google搜索一个关于定制进口商的好教程。也似乎支持svn，perforce和其他许多，但没有环绕声。

只需拍一张快照并开始一个新的git repo会更好吗？还是值得编写一个脚本来获得15年以上的代码历史？

在这种情况下，脚本可以写出来，但不是为了获取所有历史。

我建议只导入：

• 主要标签比任何一年，或者任何你觉得舒服的时期，你都不需要全面检查，因为它太旧了）


• 过去几年的所有标签（主要和未成年人）

然而，迁移到Git还需要一个工作来识别集中环绕存储库中的模块或应用程序。

尝试将所有这些数据导入到一个一个 Git仓库中是一个错误，除非它是一个不能彼此独立开发的巨大系统（比如Linux内核）。

请参阅：

• 什么是Git限制？和


• 反从cvs到分布式存储库（例如，混帐或mercurial）。初始库设计需要的建议。

My company has a large codebase in Surround SCM, which was migrated from SourceSafe a few years ago. We're looking to move to something more suited to our needs, but getting our history out of Surround is proving to be a challenge.

Googling for git importers, I found a good tutorial on custom importers. There also appears to be support for svn, perforce, and many others, but no Surround.

Would it be better to just take a snapshot and start a new git repo? Or is it worth writing a script to get 15+ years of code history?

解决方案

In this kind of scenario, a script can be written, but not for getting all the history.

I would recommend only importing:

• the major labels (for anything older than a year, or whatever period you feel comfortable you won't need the examine in full because it is so old)
• all the labels (major and minors) for the last years.

However, migrating to Git requires also a work in order to identify modules or applications within your centralized Surround repository.
Trying to import all those data into one Git repository would be a mistake, unless it is one giant system which can not be developed in parts independently one from another (like the Linux kernel).

See:

• "What are the Git limits?" and
• "Transferring legacy code base from cvs to distributed repository (e.g. git or mercurial). Suggestions needed for initial repository design."

这篇关于从环绕声SCM导入Git？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！