问题描述
我唯一的版本控制系统的经验是明确的，尽管它的目的很好，但我现在想转向一个免费工具。我已阅读并尝试使用Git& SVN，并且肯定会看到基于提交的方法的优点，而不是基于文件的方法。但是，如果其他工具中没有等价物，我会错过Clearcase的某些部分。 Clearcase可以区分用户编写的文件和用户编写的程序创建的文件。用户编写的文件将是'文件元素版本'，程序生成的文件将是'派生对象版本'。此外，可以使用clearcase cleartool catcr 命令确定派生对象版本的依赖关系。
我的问题是：在git中是否存在这些文件类型的等价物，并且存在与 cleartool catcr 命令？我同意这不是版本控制系统的严格组成部分，但如果我转移到GIT，它仍然是我想要复制的内容。
对于我来说，使用派生对象的最甜蜜的部分是从具有完整的依赖项列表cleartool catcr< flags / options> DO_name 并且真的没有更快的编译过程。
不需要 clearmake 可能正在使用。尽管如此，没有什么能比得上 cleartool catcr 的输出。
My only experience of version control systems is clearcase and, while it's served its purpose well, I would now like to move to a free tool. I've read about and experimented with Git & SVN and certainly see the advantages in the commit based approach as opposed to the file based approach that clearcase uses.
However, there are parts of Clearcase that I would miss if there is no equivalent in the other tools. Clearcase could distinguish between files that were written by the user and files that were created from programs the user had written. User written files would be 'File Element Versions' and program generated files would be 'Derived Object Versions'. Furthermore the dependencies of a 'Derived Object Version' could be determined from using the clearcase cleartool catcr command.
My question is: are there equivalents to these files types in git and is there an equivalent of the cleartool catcr command? I agree this isn't strictly part of a version control system, but it still something that I would like to replicate if I moved to GIT.
To me, the sweetest part of working with derived objects is having the complete dependency list from cleartool catcr <flags/options> DO_name and NOT really having a faster compilation process.
The closest thing to achieve that without clearmake is probably making use of gcc -MM. Still, nothing compares to the output of cleartool catcr.
这篇关于是否有一个相当于clearcase catcr的git？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！