各种 AccuRev 版本号是多少？
在 AccuRev 中，当我查看文件的历史记录（在“历史模式”下）时，我会看到对该文件执行的操作的列表。 每个操作都有一个编号 (#) 和一个版本。
当我单击其中一个操作时，会出现另一个列表，其中显示该操作中涉及的每个文件（包括我正在调查其历史记录的文件）。 该下部面板中的每个条目都有一个“虚拟版本”和一个“真实版本”。
顶部面板中的“版本”似乎与下部面板中我的文件的“虚拟版本”相同。
#、虚拟版本和真实版本有什么区别？ 为什么虚拟版本和真实版本有两个用斜杠分隔的数字？
In AccuRev, when I look at the history for a file (in "history mode"), I see a list of the actions that were taken on the file. Each action has a number (#) and a version.
When I click on one of these actions, another list appears that shows each of the files that was involved in the action (including the one whose history I'm investigating). Each entry in this lower panel has a "virtual version" and a "real version".
The "version" in the top panel appears to be the same as the "virtual version" of my file in the lower panel.
What is the difference between the #, the virtual version, and the real version? Why do virtual and real versions have two numbers separated by a slash?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我发现 AccuRev 文档令人困惑。 这是我的理解：
#是交易号。 AccuRev 仓库中的每个操作都被分配一个唯一的（自动递增）交易编号。 当一个操作影响多个文件时，它们共享事务号。
“虚拟版本”是流名称（或编号），后跟斜杠，然后是该流上的版本计数。 因此，IntegrationStream 上 helloworld.c 的第一个版本是 IntegrationStream/1，或者可能是 123/1 这样的数字。 如果 AccuRev 显示一个数字，您可以查找相应的流名称。 如果另一个流中的文件已保留多个更改，并且具有多个更改的文件最终提升到此流 (IntegrationStream)，则这只会使数字增加 1。 因此，该流上可见的下一个版本将是 IntegrationStream/2（或 123/2）。
“真实版本”是指在软件仓库中第一次看到该文件的修订版本。 这将是在某人的工作空间中执行原始保留操作时的情况。 因此，如果 IntegrationStream/2 中看到的文件版本是保留在 Proj_jsmith/7 中并提升到 IntegrationStream 的结果，则真实版本显示为 Proj_jsmith/7。
祖先、合并和补丁版本（如果适用）可以通过切换到显示祖先、合并和补丁行的“版本浏览器模式”来最好地理解。 下部面板网格中的那些列指的是与文件的给定版本相关联的版本，这些版本作为祖先或作为合并或修补程序的源。
I found the AccuRev documentation to be confusing. Here is what I've come to understand:
# is the transaction number. Every action in an AccuRev depot is assigned a unique (auto-incrementing) transaction number. When multiple files are affected in one action, they share the transaction number.
"Virtual version" is the stream name (or number), followed by a slash, followed by the count of which version it is on that stream. So, the first version of helloworld.c on the IntegrationStream is IntegrationStream/1, or perhaps a number like 123/1. If AccuRev shows you a number you can look up the corresponding stream name. If multiple changes have been kept on the file in another stream and the file with multiple changes is finally promoted to this stream (IntegrationStream), this increments the number only by one. So the next version visible on this stream would be IntegrationStream/2 (or 123/2).
The "real version" refers to the first time that revision of the file was seen in the depot. This would be when the original keep operation was performed in someone's workspace. So if the version of the file seen in IntegrationStream/2 is the result of a keep in Proj_jsmith/7 which was promoted up to IntegrationStream, then the real version shows up as Proj_jsmith/7.
The ancestor, merge and patch version, if applicable, can be best understood by switching to "version browser mode" where the ancestor, merge, and patch lines are shown. Those columns in the lower panel grid refer to the versions that are associated to the given version of a file by preceding it as an ancestor or by being the source of a merge or patch.
#是交易编号，每次换库操作都会递增，并且持续递增。AccuRev 帮助 (%PROGRAMFILES%/AccuRev/doc/WebHelp/InDepth_Real_and_Virtual_Versions.htm) 中描述了真实版本和虚拟版本之间的差异
#is the transaction number, it is incremented for each depot changing operation and is incrementing continuously.The difference between Real Version and Virtual Version is described in AccuRev help (%PROGRAMFILES%/AccuRev/doc/WebHelp/InDepth_Real_and_Virtual_Versions.htm)