您要查找的是不是：
- The SCM tool is responsible for keeping track of everything. 源码控制工具有责任追踪任何事情。
- The SCM tool must be explicitly informed of all changes to the working folder. 配置管理工具必须明确所有工作目录中发生的变更。
- A good SCM tool must do more than just keep every version of everything. 一个好的配置管理工具必须做出更多事情来保持所有文件的任何版本。
- Yes, the SCM tool will make that merge easy, but you still have to do it. 是的，源码控制工具将容易的合并，但是你还是要亲自去做。
- Unfortunately, SCM tools are unique. 不幸的是，配置管理工具是唯一的。
- The answer varies across SCM tools. 答案对于配置管理工具而言是各种各样。
- Not all SCM tools work the way I have described. 不是所有的配置管理工具都通过这种我描述过的方式进行工作。
- Over time, the design of SCM tools matured. 时光流逝，配置管理工具的设计成熟了。
- I confess that not all SCM tools work this way. 我承认不是所有的配置管理工具都是用那种方式工作。
- The SCM tool's Checkout command not only informs the server of the checkout request, but it also flips the bit on the working file to make it writable. 配置管理工具的签出命令不只是告诉服务器签出的请求，它还请求将工作文件变更为可写。
- That sounds okay, but it doesn't justify the development of a full blown SCM tool to meet this end! 听起来有些道理,但并不能要求所有成熟的的这个想法吧?
- Your SCM tool may record the timestamp on the working file, so that it can later detect if you have modified it. 你的配置管理工具可以在工作文件上记录时间戳，所以它在你修改的时候可以监测到。
- Some SCM tools can be configured to behave either way. 一些配置管理工具可以通过设置来满足所有这些方式。
- Some SCM tools use some sort of a compromise design. 一些配置管理工具使用了一些折中的设计。
- It is while using the history features of an SCM tool that we notice what a lousy job our developers do on their checkin comments. 在使用一个配置管理工具的历史特性的时候，我们发现我们的开发人员在他们签入注释中做了很恶心的工作。
- Often this is implicitly understood to be the latest version, but your SCM tool will almost certainly allow you to label something in the past. 通常隐含的理解是最近的版本，但是配置管理工具也几乎都允许你为过去的版本定义标签。
- Most SCM tools ask the user to enter a comment when making a checkin. 大多数的配置管理工具要求用户签入的时候输入注释。
- The developer would simply work, making all kinds of changes to the working folder while the SCM tool eavesdrops, keeping an accurate list of every change that has been made. 开发人员可以单纯的工作，在配置管理工具监听的状态下在工作目录中进行各种变更，还能够对已经做的变更有一个精确的列表。
- Most SCM tools offer the ability to have multiple distinct repositories. 许多配置管理工具都可以建立许多不同的库。
- Implementing an SCM tool based on this standard - and not on some proprietary technology the way Perforce does - is in line with SAP's strategy of creating 'open-ended' systems. 如果用此标准来进行软件配置管理，就与SAP创建可修整（open-ended）系统的想法不谋而合。Perforce可没有采用这种技术。”
