In general , the recommended way to fix a problem is to checkin a new version which fixes it 通常，解决这个问题的建议是在修改的时候签入一个新的版本。
However , this looseness is typical of the way people use the word " checkin " , so you ' ll get used to it 当然，这种随意就是人们使用“签入”的典型的方式。
If you use a code generation tool , checkin the input file , not the generated code file 如果你使用一个代码生成工具，签入这个输入文件，不是生成的代码文件。
Never checkin your changes without giving them a quick review in some sort of a diff tool 一定不要在没有通过任何比较工具进行一个快速回顾前就签入你的变更。
Each checkin adds to the history of our repository . we never subtract anything from that history 每个签入在我们的配置库中添加了历史。我们不能从历史里面减去什么东西。
Users who prefer " checkout - edit - checkin " actually have a somewhat more consistent rule for their work 实际上喜欢使用“签出修改签入”的用户对他们的工作要多点固定的规则。
I believe developers should be encouraged to enter checkin comments which are as long as necessary to explain what is going on 我认为开发人员应该被鼓励在必要的解释的时候输入签入的注释。
It may seem odd to refer to these operations using the word " checkin " , because there is no corresponding " checkout " step 看起来这些操作使用“签入”是很零散的，因为没有相应的“签出”步骤。
For users who use the checkout - edit - checkin style of development , closely related here is the need to undo a checkout 对于使用签出编辑签入风格进行开发的用户，类似描述就是需要撤销签出。
If you generate your product documentation in several different formats , checkin the original format , the one that you manually edit 如果你用几种不同的格式生成你的产品文档，签入你手工编辑的原始格式。
