全部

1·This is because we need similar skills and knowledge to support that product on each code branch — that is, that development activity related to each product version.

这是因为我们需要相似的提示和知识来支持每一个“编码分支”——与每个产品版本相关的开发活动——上的产品。

2·Merge down the latest from the work branch, and check in your code.

从工作分支中取得并合并最新的代码，然后检入你的代码。

3·Each team has their own work branch, since they each need somewhere to test their code before publishing to the trunk.

由于每个团队都要在发布代码到主干前进行测试，因此他们有各自的工作分支。

4·Another option is to create a new workbench project by importing code from the selected branch of the CVS repository.

另一个选项是通过从选定的CVS资源库分支导入代码来创建新的工作台项目。

5·Developers can have the freedom to flesh out concepts outside of the main code branch without impacting stable configurations.

开发人员可以在主代码分支之外自由地试验新概念，而不会影响稳定的配置。

6·At that point we can (and should) publish to the trunk, i.e. take all new code on the work branch and copy over to the trunk.

此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。

7·If the compiler has this prediction information, it can generate the most optimal code around the branch.

如果编译器知道这种预测信息，就可以围绕最可能执行的分支生成最优的代码。

8·After the previous test, Process a and Process Z diverge, each taking a separate code path, as if both came to a fork in the road and each took a distinct branch.

在上次测试之后，进程a和进程z会出现差异，每个进程会采用单独的代码路径，就像路上出现岔道，每一个都会走上不同的分枝。

9·You can measure code coverage in several ways: by assessing line or statement coverage, condition coverage, branch coverage, and so on.

您可以通过许多方法来测量代码覆盖率：通过评估代码行或语句的覆盖面、条件覆盖面、分支覆盖面等等。

10·The JIT compiler may produce incorrect code that either references or attempts to branch to an invalid location.

JIT编译器可能生成错误代码，该代码引用或尝试对无效的位置进行分支。