在合理的大写情况下配置规范 [英] Config spec in rational clearcase

问题描述

对于这些清晰的案例工具，我实在是太陌生了。我正在学习，因为我有一个项目要进行。
i刚刚了解到默认配置规范是

I am so much new to these clear case tool.I am learning because i have a project to work on. i just learned the default config spec is

element *CHECKEDOUT
element */main/LATEST 

因此，新版本是在 main 分支中创建的在以前的版本之后。

但是我一直在尝试这些，我只是将配置规范更改为这些

So the new version is created in the main branch after the previous version.
But I have been trying these, and I just changed my config spec to these

element *CHECKEDOUT
element */main/2

在这些设置之后，当我单击显示 找不到文件的文件：我无法检入或检出。

然后我更改为默认配置，使其再次正常工作。

After those settings, when I click the file it says "file not found": I cannot check in or check out.
And then I changed to default config spec its working again.

怎么了？

还告诉我这些如何去 version 4 如果我的最新版本是 main 中的6，在那儿创建一个分支？

Whats wrong?
Also tell me these How can I go to a version 4 to create a branch over there if my latest version is 6 in main ?

推荐答案

通过选择规则：

 element */main/2

您指示ClearCase仅向您显示...的版本2 ...

You instruct ClearCase to only show you "version 2" of... Everything:

 /my/path/to/a/File

如果 aFile 的任何父目录还没有版本2，您将无法访问 aFile 。

So if any of the parent directory of 'aFile' has no "version 2' yet, you won't be able to access aFile.

您应始终在端保留 / main / LATEST 选择规则（如果之前的任何规则不起作用），以退回该通用规则（之所以通用，是因为任何元素至少具有其版本0 存储在 main 分支中，除非 main 具有被重新命名h非常不好）

You should always keep a '/main/LATEST' selection rule at the end of your config spec in order, if any of the previous rules don't work, to fall back to that one universal rule (universal because any element has at least its version 0 stored in the 'main' branch, unless 'main' has been renamed, which is very bad)

例如：

 element * CHECKEDOUT
 element * /main/2
 element * /main/LATEST

将工作，并且会向您显示所有版本的版本2 ，如果没有，则显示最新版本。

will work, and will show you version 2 of everything if they have one, or the LATEST version if they don't.

当您要从某个点创建分支时，最好不要依赖版本号（因为所谓的版本4仅对文件有效，对目录无效）。

不要忘记文件和目录是在元素基础上进行版本控制的：您先对文件进行版本控制，然后对目录进行版本控制，然后再对另一个文件进行……...：它以文件为中心，而不像其他VCS那样以存储库为中心（ SVN，Git，Mercurial ...），其中包含一个原子提交和所有存储库的一个修订版号：在这里，您为每个元素（文件或目录）具有单个版本号）。

请参阅 每个开发人员应了解的ClearCase基本概念是什么？了解更多信息

When you want to create a branch from a certain point, it is best to not rely on a version number (because what you call 'version 4' is only valid for your file, not for your directory).
Don't forget that files and directory are versioned in a element-basis: you version a file, then a directory, then another file...: it is file-centric, not repository-centric like other VCS (SVN, Git, Mercurial, ...) with an atomic commit and one revision number for the all repo: here you have individual version number for each element (file or directory).
See "What are the basic ClearCase concepts every developer should know?" for more

但是如果您没有标签，我的建议是：

But if you don't have a label, my advice would be to:

• 确定一个时间点，在该时间点，您的代码处于分支机构想要的状态


• 进行< a href = https://stackoverflow.com/questions/634509/clearcase-loading-older-version-of-a-specific-directory>基于时间的选择规则


• 使用mkbranch指令完成该选择规则


• 不要忘记您将在该分支上添加的新文件（即' / main / 0 '规则）

• determine a point in time where your code where at the state you want it to be for your branch
• make a time-based selection rule
• complete that selection rule with a mkbranch directive
• don't forget the new files you will add on that branch (that's the '/main/0' rule)

因此：

element * CHECKEDOUT
element * .../myBranch/LATEST
element * /main/LATEST -time dd-Month-yyyy -mkbranch myBranch
element * /main/0 -mkbranch myBranch
element * /main/LATEST 

将创建一个新分支' myBranch '对于最多在dd-Month-yyy日期创建的任何元素。

will create a new branch 'myBranch' for any element created at most at the dd-Month-yyy date.

这篇关于在合理的大写情况下配置规范的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！