在透明盒上使用水银时保留历史记录 [英] preserving history when using mercurial ontop of clearcase

问题描述

我在ClearCase商店工作，尽管我们的代码审查流程阻止我使用它来跟踪我的日常更改，但CC在整合团队工作方面做得很好.在我的CC视图顶部创建hg存储库效果很好.我可以跟踪自己的更改，并轻松地在文件服务器上进行备份，为人们产生差异等.

I work in a ClearCase shop and CC does a good job of integrating the team's work though our code review process prevents me from using it to track my daily changes. Creating an hg repository on top of my CC view works really well. I can track my changes and easily make backups on the file server, produce diffs for people etc.

这一切都很好，直到我转到新的CC视图并且不得不将自己的历史抛在脑后.我希望能够拉?我以前的历史记录，并且在新视图中显示的所有不同内容都显示为最新更改集.

This is all well and good until I move to a new CC view and have to leave my history behind. I would love to be able to ?pull? my previous history in and have everything that's different in the new view show up as the latest change set.

推荐答案

我们在ClearCase静态视图中使用Git，原因与您描述的原因大致相同-细粒度的控件.

We use Git inside a ClearCase static view, for pretty much the same reason you described - finer grained control.

在CC中，当我们开始处理较新的(带有标签的)发行版并且配置规范进行了适当更改时，Git会将其作为常规更改集使用.

In CC, when we start working on a newer (labelled) release and the config spec changes appropriately, Git picks that up as a regular changeset.

魔术之所以有效，是因为Git对配置规范一无所知，而CC对.git目录一无所知.当配置规范更改时，它将重新加载已更改的所有文件，但不会触及.git目录，因此Git仍然可以看到该存储库.

The magic works precicely because Git knows nothing about config specs, and CC knows nothing about the .git directory. When the config spec changes, it reloads whatever files have changed but doesn't touch the .git dir, so Git still sees the repo.

我没有使用Mercurial的经验，但是我只是将其启动，并添加了一些目录和文件，看来它的工作方式相同.

I don't have any experience with Mercurial, but I just fired it up then and added a few dirs and files, and it appears that it works the same way.

这篇关于在透明盒上使用水银时保留历史记录的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！