如何使用 TortoiseSVN 和 Subversion 在新分支中提交当前更改？
我所处的情况是我不想将当前的更改提交到主干。
我想加入一家私人分支机构并在那里工作一段时间，直到我确定一切正常。我会将分支中所做的更改合并到主干。
当您使用 Subversion 和 TortoiseSVN 时，推荐的步骤是什么？
我有经典的目录结构：
- /trunk
- /branches
- /tags
I'm in a situation where I don't want to commit my current changes to the trunk.
I would like to commit to a private branch and work there a little until I'm sure that everything is OK. I will merge changes made in my branch to the trunk.
What is the recommended procedure when you use Subversion and TortoiseSVN?
I have the classic directory structure:
- /trunk
- /branches
- /tags
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这是 TortoiseSVN 中的一个选项。从上下文菜单中单击“分支/标签...”，然后从标有“在存储库中创建副本：”的单选按钮中选择“工作副本”，新分支将来自您的工作副本。
在到路径文本框中，添加具有正确的“/branches/”路径的路径，以确保它符合您提到的结构（branches/tags/trunk）。不要忘记给你的分支起一个有意义的名称，我发现在注释中输入我所分支的主干的修订号很有用。
或者，单独从主干创建分支，然后将工作副本切换到新分支，保留工作副本，并从那里提交到分支。
This is an option in TortoiseSVN. Click on Branch/tag... from the context menu, then choose "Working copy" from the radio buttons labeled "create copy in the repository from:" and the new branch will come from your working copy.
In the To path textbox, add in the path with the correct "/branches/" path to make sure it conforms to the structure you mentioned (branches/tags/trunk). Don't forget to give your branch a good meaningful name, and I find it useful in the comments to put in the revision number of the trunk which I'm branching from.
Alternatively, create the branch from the trunk separately, then switch your working copy to the new branch, preserving your working copy, and commit to the branch from there.
现在有一个实验性的仅限客户端选项，可以从上下文菜单中“搁置”更改。这会以您指定的名称收集客户端上的更改。由于这些更改不会存储在存储库中，因此其他人将看不到它们。您稍后可以“取消搁置”它们以取回您的更改。有关更多详细信息，请参阅文档页面。
主要需要注意的是搁置是实验性的。如果格式发生更改，升级 SVN 客户端可能会使现有搁置的更改集失效。
There is now an experimental client-only option to "Shelve" changes available from the context menu. This gathers the changes up on the client under a name you give them. Since these changes will not be stored in the repository, they will not be visible to others. You can later "Unshelve" them to get your changes back. See the documentation page for more details.
The main caveat is that Shelving is experimental. Upgrading your SVN client may invalidate existing shelved change sets should the format change.