SVN - 提交到较旧的修订版本
我们在服务器上有一个 svn 存储库，并且一些客户端更新/提交它。
现在，服务器昨天崩溃了，可用的备份已经一周了，并且保存了较旧的 svn 头。假设备份中的头是修订版 2895。
但是客户端有修订版，即。 2930. 当我尝试提交到服务器时，收到一条错误消息，指出服务器上的修订版本较旧。我无法签入，无法升级，也无法提交。
有谁知道我可以做什么来增加服务器上的修订计数器，或者如何在这种情况下进行提交？
提前致谢。
we have a svn repository on a server, and some clients updating/commiting to it.
Now, the server crashed yesterday and the backup available is a week ok old, and has an older svn head saved. Let's say the Head from the backup is revision 2895.
The clients however have revision ie. 2930. When I try to commit to the server, I get an error that the revision on the server is a older one. I can't check in, I can't upgrade and I can't commit.
Has anybody an idea of what I can do to either increment the revision's counter on the server, or how to make a commit under this circumstances?
Thanks in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您可以在 rev2930 制作工作副本的非版本控制临时副本，将 rev2895 检出到新文件夹，用您制作的副本覆盖并提交到 rev2896。这将要求其他人做类似的事情（如果他们的工作副本没有任何更改，他们可以从 rev2896 中查看新的工作副本）。
You can make a non-versioned temporary copy of the working copy at rev2930, check out rev2895 to a new folder, overwrite with the copy you made and commit to rev2896. This will require everyone else to do something similar (if they don't have any changes in their working copy, they can just check out a new working copy from rev2896).
一种解决方案是在新文件夹中签出并用修改后的文件替换文件，然后尝试提交。
我不是专家，但可能有更优雅的解决方案。
One solution is to make a checkout in a new folder and replace the files with the modified ones, then try to commit.
I'm not an expert and there may be a more elegant solution though.
您不能在本地复制 2930，恢复到 2895，然后将所有内容提交回 2896 吗？
Can't you copy locally your 2930, revert to 2895 and then commit everything back to 2896?