使用基于早期版本的工作副本时提交 Tortoise-SVN 的行为
今天早上，我对工作副本的文件夹结构进行了一系列更改，遇到了巨大的问题，这些更改已提交到存储库。我决定最好的办法就是回到昨天晚上的提交并重新开始。
我已经删除了我的工作副本，并根据昨天晚上的提交检查了另一个工作副本。
鉴于这不是 HEAD 修订版，我不确定当我从新工作副本提交时会发生什么。 SVN 会以某种方式尝试合并我今天早上所做的提交（我绝对不想要），还是只会提交我自签出工作副本以来所做的更改，并基于此创建一个新的 HEAD 修订版？
I have had massive problems with a serious of changes made to the folder structure of my working copy this morning, which have been committed to the repository. I have decided the best thing to do is to go back to yesterday evening's commit and start again.
I have deleted my working copy and checked out another one based on yesterday evening's commit.
Given that this isn't the HEAD revision, I'm not sure what happens now when I commit from the new working copy. Will SVN somehow try to incorporate the commits I made this morning (which I definitely don't want), or will it commit only the changes I've made since checking out the working copy, and create a new HEAD revision based on that?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
使用以下命令删除不需要的提交。而修订版 302 可能是您再次查看的版本。撤消操作可以在存储库上完成。
撤消更改中有更详细的描述。
您的工作副本必须达到日期以便提交更改。 您将无法提交更改。
如果没有我希望您不介意命令行方法，
Use the following command in order to remove the unwanted commit. Whereas Revision 302 might be the one you checked out again. The undo operation can be done on the repository.
is described in further detail in Undoing Changes
Your working copy must be up to date in order to commit changes. You won't be able to commit your changes without an
I hope you don't mind the command line approach.