Clearcase视图和分支说明 [英] Clearcase View and Branch explained

问题描述

我最近开始研究一个新项目，开发团队正在使用该项目使用ClearCase进行版本控制（该项目大多使用Java和ExtJs进行编码）。

I've recently started working on a new project for which the development team is using ClearCase for version control (the project is coded mostly in java and ExtJs).

我听说查看和分支这两个术语经常被使用-这些术语可以互换吗？

如果不是，可以您请提供关于视图和分支的外行说明，以及它们之间的关系。

I'm hearing the terms 'View' and 'Branch' being thrown around a lot - are these terms interchangeable?
If not, could you please provide a layman's explanation of a View and a Branch and how they relate to each other.

ClearCase是否具有特定的视图和分支，或者这些术语是否也在其他版本控制系统中使用？

Are Views and Branches particular to ClearCase or are these terms used in other version control systems as well?

推荐答案

我听到了很多视图和分支这样的术语-这些术语可以互换吗？

I'm hearing the terms 'View' and 'Branch' being thrown around a lot - are these terms interchangeable?

否：

• 视图是一种选择元素版本的方法（文件或目录）
  
  这样，您可以从不同分支中选择版本。


• 分支是版本的集合，带有分支点。
  
  每个分支均以 占位符版本 （版本 0 ： / main / 0 标记元素的创建，而 / main / aBranch / 0 标志着创建了一个新分支，一个分支，该分支的版本与先前的分支相同）

• A view is a way to select versions of elements (files or directories)
  As such, you can select versions from different branches.
• A branch is a collection of versions, with branching points.
  Each branch starts with a placeholder version (the version 0: /main/0 marks the creation of the element, while /main/aBranch/0 marks the creation of a new branch, a forking point, where the version remains identical to the previous one)

更多信息请参见 关于分支，版本和标签：

将资源添加到ClearCase源控件时，将在VOB中创建表示该资源的元素。

该元素具有一个名为main的分支和一个版本（版本0）。 ）在该分支上。可以在主分支上创建该元素的后续版本，并在必要时创建其他分支

When you add a resource to ClearCase source control, an element representing that resource is created in the VOB.
The element has a single branch named main and a single version (version 0) on that branch. Successive versions of the element can be created on the main branch, and additional branches can be created if necessary

版本树中的每个分支都包含该元素的一个或多个版本。每个版本都代表该元素的修订版。

版本使用扩展版本的路径名来标识，该路径名包括其VOB中元素的路径名，并在其上指定其分支名称和版本号。科。例如，文件 module.java 的第四次修订版位于VOB目录 \product\src\ 具有版本扩展路径名 \product\src\module.java @@ \main\4 。

Every branch in a version tree includes one or more versions of the element. Each version represents a revision of the element.
Versions are identified using a version-extended path name, which includes the path name of the element within its VOB and also specifies its branch name and its version number on that branch. For example, the fourth revision of the file module.java, located on the main branch in the VOB directory \product\src\ has the version-extended path name \product\src\module.java@@\main\4.

另请参见 使用属性选择版本的视图作为高级配置规范示例。

See more also at "View that uses attributes to select versions" for an advanced config spec example.

ClearCase的视图和分支还是特定于其他版本控制系统的术语？

Are Views and Branches particular to ClearCase or are these terms used in other version control systems as well?

视图（尤其是动态视图）特定于ClearCase。

但是它们所代表的不是：它是一个a的组合工作目录和版本选择机制。您会在大多数版本控制系统中找到它。

Views, especially dynamic views, are specific to ClearCase.
But what they represent is not: it is the combination of a working directory and a version selection mechanism. You find that in most version control system.

分支是所有VCS的一部分，并启用合并工作流程。

请参阅 与ClearCase策略相比，如何使用git元数据策略？例如，与git相比。

Branches are part of all VCS, and enables a merge workflow.
See "How to use git metadata strategies compared to ClearCase ones?" to see that compared with git, for instance.

这篇关于Clearcase视图和分支说明的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！