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.
这是因为我们需要相似的提示和知识来支持每一个“编码分支”——与每个产品版本相关的开发活动——上的产品。
Merge down the latest from the work branch, and check in your code.
从工作分支中取得并合并最新的代码，然后检入你的代码。
Each team has their own work branch, since they each need somewhere to test their code before publishing to the trunk.
由于每个团队都要在发布代码到主干前进行测试，因此他们有各自的工作分支。
Another option is to create a new workbench project by importing code from the selected branch of the CVS repository.
另一个选项是通过从选定的CVS资源库分支导入代码来创建新的工作台项目。
Developers can have the freedom to flesh out concepts outside of the main code branch without impacting stable configurations.
开发人员可以在主代码分支之外自由地试验新概念，而不会影响稳定的配置。
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.
此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。
If the compiler has this prediction information, it can generate the most optimal code around the branch.
如果编译器知道这种预测信息，就可以围绕最可能执行的分支生成最优的代码。
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会出现差异，每个进程会采用单独的代码路径，就像路上出现岔道，每一个都会走上不同的分枝。
You can measure code coverage in several ways: by assessing line or statement coverage, condition coverage, branch coverage, and so on.
您可以通过许多方法来测量代码覆盖率：通过评估代码行或语句的覆盖面、条件覆盖面、分支覆盖面等等。
The JIT compiler may produce incorrect code that either references or attempts to branch to an invalid location.
JIT编译器可能生成错误代码，该代码引用或尝试对无效的位置进行分支。
When working with conditional code, you often know which branch is most likely and which is not.
在开发人员使用有条件代码时，常常知道最可能执行哪个分支，而哪个分支很少执行。
A code coverage tool reports test coverage — either in the form of line or branch coverage — that represents the amount of code that is being touched when a test is run.
代码覆盖工具可报告测试覆盖率——以行覆盖或分支覆盖形式表示——它表示测试运行时所涉及的代码量。
Remember that the point of removing the branch was so that you can vectorize the code.
请记住：删除分支的目的在于对代码进行向量化。
Finally, notice that the branch target for the function call is not the code that starts it, but the.opd entry point descriptor.
最后，请注意函数调用的分支目标并不是启动它的代码，而是.opd入点描述符。
Once every method has at least one test, use a code coverage tool, such as Cobertura, to write one test for every branch until each line of code is tested.
当每个方法都有了至少一个测试，使用一个代码覆盖率工具如cobertura为每个分支编写一个测试，直到每一行代码都能够被测试。
The code lines 219-226 contains the actual SQL statement used in Distributed Transaction for the corresponding branch.
第219- 226行代码包含了分布式事务(Distributed Transaction)中为相应分支所使用的真正sql语句。
For example, if the conditional is marked "likely" then the compiler can place the True portion of the code immediately following the branch (which will not be taken).
例如，如果一个条件标上了“likely”，那么编译器可以把代码的True部分直接放在分支指令后面(这样就不需要执行分支指令)。
In Figure 2, I've done this for the first reported failure, a branch not completely covered. Listing 3 shows the detailed failure message, along with a snippet of the code it's pointing at.
在图2中，我对报告的第一个失败采用了这种方法，报告的这个失败是一个没有完全覆盖的分支。
Each branch, loop, or other logic added to the source code is preceded by the writing of an atomic test that will exercise that outcome.
每个分支、循环，或其他逻辑在加入源代码之前都要写出将要执行结果的自动化测试。
The other possible branches in the code are either inline functions (which can, obviously, be inlined by the compiler), or are easily branch-eliminated by the compiler.
其他代码要么是内联函数(显然可以由编译器进行内联)，要么是可以由编译器轻松消除分支的代码。
Merges are a key aspect of a source code control system in general and are especially common in a branch-oriented VCS.
合并一般是源代码控制系统中的关键方面，在面向分支的VCS尤其常见。
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.
这是因为我们需要相似的提示和知识来支持每一个“编码分支”——与每个产品版本相关的开发活动——上的产品。
Examples of tagging source code for a branch.
举例说明如何标记分支的源代码？
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.
此时我们可以(而且应该)将此分支公开发布到主干上，比如将工作分支上所有的新代码复制到主干上。
In those cases where neither Squirrel Shell nor you can abstract the platform away, Squirrel Shell provides a handy function to probe the operating system so code can follow an appropriate branch.
在这些情况下，无论是SquirrelShell还是您都无法脱离平台，Squirrel Shell提供了一个方便的函数来探测操作系统，这样代码就可以适当的执行。
The functionality however 16 is already available via the Mercurial source code repositories default branch 17 and is actively being used by several RabbitMQ users.
但是，这个功能16可以通过使用Mercurial代码库的默认branch17来实现，而且已经有一些RabbitMQ用户在使用了。
The HEAD stream is the main code stream that users should be integrating to (if they want to branch off on their own and then merge with the HEAD stream later, that's fine).
HEAD条目是用户应集成的主要代码流(如果它们需要自己分叉并稍后与HEAD流合并，这主意不错)。
The HEAD stream is the main code stream that users should be integrating to (if they want to branch off on their own and then merge with the HEAD stream later, that's fine).
HEAD条目是用户应集成的主要代码流(如果它们需要自己分叉并稍后与HEAD流合并，这主意不错)。
应用推荐