Changeset versus snapshot models.
变更集模型与快照模型。
You can delete a shelveset but you cannot delete a changeset.
您可以删除搁置集，但无法删除变更集。
tags: Used when you release software to identify a changeset for later use.
标记：在发布软件时用于标识变更集，以备使用。
Tracking Changeset window switches to a view that shows the sequence of the merges.
“跟踪变更集”窗口将切换到一个显示合并序列的视图。
Tracking Changeset window, you can determine which branches have and have not received a set of changes.
追踪变更集视窗，您可以判断哪些分支已接收到或者未接收到变更集。
TheDetails for Changeset window opens and shows the list of source files that are associated with the changeset.
“变更集的详细信息”窗口打开并显示与该变更集关联的源文件的列表。
The changeset model requires less space, but it may take more time to get a particular revision because a delta must be applied to the base revision.
而变更集模型需要的空间少，但需要更多时间来获得某个修订，原因是delta必须应用于基本修订。
Associating Completed work with a Changeset: When coding changes are checked in, you must make sure that they are associated with a work item that they resolve.
建立已完成工作与变更集的关联：当签入程序码变更时，您必须确定它们已与其解析的工作项目产生关联。
The branches to which the changeset has not been merged (for example, FeatureB and Main in the previous illustration) appear in white at the bottom of the view.
尚未合并变更集的分支 （例如，上图中的「功能 B」和「主要」） 会以白色出现在检视的底端。
You can prevent or at least, strongly discourage users from creating changeset that do not comply with established team standards by creating and enforcing check-in policies.
您可以建立并强制执行签入原则，藉以防止或至少强烈建议使用者不要建立与已确立小组标准不符的变更集。
To minimize the number of patches that must be applied to a base revision (per the changeset model), the cacherev command will create a new snapshot of the base revision in the repository.
为了最小化必须应用到基本修订的修补的数量（根据变更集模型），cacherev命令将会在存储库中创建基本修订的一个新的快照。
To minimize the number of patches that must be applied to a base revision (per the changeset model), the cacherev command will create a new snapshot of the base revision in the repository.
为了最小化必须应用到基本修订的修补的数量（根据变更集模型），cacherev命令将会在存储库中创建基本修订的一个新的快照。
应用推荐