您只能在颠覆历史记录的头部提交新的更改。

你不能直接用你电脑上的好拷贝做任何事情的原因是，它的.svn文件夹知道它是过去的代码，所以在提交之前需要更新。

找到好的修订号并恢复

Find the revision number of the old copy you want. Get your current revision with: svn info --show-item revision # or svn log Or to check older versions of your project, use: svn update -r <earlier_revision_number> until you find the right revision number. Note down the good revision number (assuming 123 for examples below). Update to the latest revision: svn update Undo all the changes between the revision you want and the latest version: svn merge -r HEAD:123 . svn commit -m "Reverted to revision 123" (the same as Jon Skeet's answer above.)

如果你找不到修订号

如果你找不到旧的副本，你只想提交当前在你的电脑上的文件:

Make a copy of your good version (but without any .svn folders): cd .. rsync -ai --exclude=.svn project/ project-good/ Now make sure you have the latest version: cd project svn update # or make a fresh checkout svn checkout <url> Copy your good version over the top of the working copy. This command will copy, and also delete any files from the working tree that aren't in your good copy, but it won't affect the existing .svn folders. cd .. rsync -ai --exclude=.svn --delete project-good/ project/ If you don't have rsync, you can use cp -a but you will also need to delete any unwanted files manually. You should be able to commit what you have now. cd project svn commit -m "Reverted to good copy"

就用这条线

svn update -r yourOldRevesion

您可以使用以下命令了解您的当前版本:

svn的信息

以前的大多数答案都是使用反向合并，这通常是正确的答案。然而，有一种情况(刚刚发生在我身上)却不是这样。

我不小心将一个Unix行结束符的文件更改为DOS行结束符时做了一个小更改，并提交了它。这很容易取消，可以通过更改行结束符并再次提交，也可以通过反向合并，但它的效果是使svn blame list my edit作为文件每一行的源。(有趣的是，Windows上的TortoiseSVN不受此影响;只有命令行责备SVN。)

如果要维护svn blame上报的历史记录，我认为需要做以下工作:

删除文件并提交。 在存储库中，将文件先前的良好副本复制到头文件中，并提交。 恢复您想要保留的任何编辑。

删除有点可怕，但请记住，您始终将文件保存在存储库中，因此恢复它不是什么大问题。下面是一些演示步骤的代码。假设xxx是最后一个好的副本的修订号。

svn rm svn+ssh://path/to/file
svn copy svn+ssh://path/to/file@xxx svn+ssh://path/to -m"Restore good copy"
svn update
<restore the edits>
svn commit -m"Restore edits"

注意，对于存储库中的副本，目标需要是目录，而不是文件名。

您只能在颠覆历史记录的头部提交新的更改。

你不能直接用你电脑上的好拷贝做任何事情的原因是，它的.svn文件夹知道它是过去的代码，所以在提交之前需要更新。

找到好的修订号并恢复

Find the revision number of the old copy you want. Get your current revision with: svn info --show-item revision # or svn log Or to check older versions of your project, use: svn update -r <earlier_revision_number> until you find the right revision number. Note down the good revision number (assuming 123 for examples below). Update to the latest revision: svn update Undo all the changes between the revision you want and the latest version: svn merge -r HEAD:123 . svn commit -m "Reverted to revision 123" (the same as Jon Skeet's answer above.)

如果你找不到修订号

如果你找不到旧的副本，你只想提交当前在你的电脑上的文件:

Make a copy of your good version (but without any .svn folders): cd .. rsync -ai --exclude=.svn project/ project-good/ Now make sure you have the latest version: cd project svn update # or make a fresh checkout svn checkout <url> Copy your good version over the top of the working copy. This command will copy, and also delete any files from the working tree that aren't in your good copy, but it won't affect the existing .svn folders. cd .. rsync -ai --exclude=.svn --delete project-good/ project/ If you don't have rsync, you can use cp -a but you will also need to delete any unwanted files manually. You should be able to commit what you have now. cd project svn commit -m "Reverted to good copy"

我认为这是最合适的:

是否合并向后，例如，如果提交的代码包含修订 5612到5616版本，倒着合并。对我来说很管用。

例如:

svn merge -r 5616:5612 https://<your_svn_repository>/

它将包含一个合并的代码回到以前的修订，然后您可以提交它。

基本上你需要“向后合并”——将当前版本和以前版本之间的差异应用到当前版本(因此你最终会得到一个看起来像旧版本的工作副本)，然后再次提交。例如，从150版(目前)回到140版:

svn update
svn merge -r 150:140 .
svn commit -m "Rolled back to r140"

Subversion红皮书对此有一个很好的章节。