是否有可能将MKS Integrity存储库导入到git中？ [英] Is it possible to import an MKS Integrity repository into git?

问题描述

我只需要源代码树及其历史。我现在不关心需求/问题。我玩了一下这个命令行来弄清楚我是否可以得到主干和一些开发路径的更改包列表。我认为应该有可能为每个更改包提取一个diff，并使用它来重放自第一次提交git以来的所有更改。就像这样：

1. 获得第一次提交并将其添加到git中


2. 获取下一个CP
li>

3. 获得CP的差异
   
4. 将diff应用于git working dir


5. 添加并提交对git的更改
>

6. 重复（2.）直到最后一个CP

您也可以使用checkpoint对我来说是足够好的）。

更简单的方法是只检出一个CP并添加/提交给git。但是，那么你会忽略添加，删除，移动和重命名操作。

有人知道如何从si diff中获得统一差异吗？这已经有很大的帮助了。

有什么想法？

Edit2： >
添加了一个答案，显示了我是如何实现迁移的......

解决方案

MKS Integrity 是其独特的存储库，其中 everything 所在：

• 需求，
  
• 测试计划，
  
• 测试用例，
>

• 特性，
  
• 开发人员任务，
  
• 部署请求

由于这些数据可以彼此独立演变，按照自己的步调，将它们全部导入到一个Git存储库中将是一个坏主意：您只能克隆所有 Git仓库的内容（即使您可以限制该克隆的深度）。

这意味着即使您只是对代码感兴趣，您也将获得所有文档。

MKS诚信博览会rt意味着要定义第一批许多Git存储库，以充当子模块。

---

我只需要源代码树及其历史记录。

像往常一样，我建议只导入：

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


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

除非您确信所有源代表 ，否则我不会将其全部导入 >一个系统开发为全部（而不是独立开发的几个模块）

更简单的方法是仅仅签出一个CP并添加/提交给git。

这将是继续进行的方式。

但是，那么您会忽略添加，移除，移动和重命名操作。

不！你不会！ Git会 推断这些操作 。
这是作为一个文件的优势 内容 VCS 。

I need only the source tree and its history. I don't care for the requirements/issues stuff for now. I played a bit witth the command line to figure out if I could get a list of change packages for the trunk and some of the dev paths. I thought it should be possible to extract a diff for every change package and use that to replay all the changes since the first commit in git. Something like this:

1. get first commit and add it to git
2. get next CP
3. get diff for CP
4. apply diff to git working dir
5. add and commit changes to git
6. repeat with (2.) until last CP

You could also repleace change package with checkpoint (would be good enough for me).

A simpler way would be to just checkout a CP and add/commit to git. But then you would loose track of add, remove, move and rename operations.

Does anyone know how to get a unified diff from "si diff"? That would already help alot.

Any ideas?

Edit2:
Added an answer that shows how I actually did the migration...

解决方案

The problem with MKS Integrity is their unique repository in which everything resides:

• requirements,
• test plans,
• test cases,
• features,
• developer tasks,
• deployment requests

Since those data can evolve independently one from another, at their own pace, importing them all in one Git repository would be a bad idea: you can only clone all the content of a Git repo (even if you can limit the depth of that clone).
That means you will get all the documents, even though you are just interested in the code.
An MKS Integrity export would imply to define first many Git repositories to act as submodules.

---

I need only the source tree and its history.

As usual, 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.

And I would not import all in one Git repository unless you are confident that all your sources represents one system developed as a all (and not several "modules" developed independently)

A simpler way would be to just checkout a CP and add/commit to git.

That would be the way to proceed.

But then you would loose track of add, remove, move and rename operations.

No! You would not! Git will infer those operations.
That is the advantage of being a file Content VCS.

这篇关于是否有可能将MKS Integrity存储库导入到git中？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！