Tortoise SVN 存储库已损坏 - 我们可以将工作副本提交到存储库的旧备份吗？
不幸的是，我们的 tortoiseSVN 存储库今天由于磁盘故障而损坏。
我们有一个基于修订版 2897 的良好工作副本。 我们最新的备份存储库来自修订版 2848。
我们希望尽可能多地挽救历史记录，而不是启动新的存储库。
那么，我们可以通过将工作副本直接提交到旧的备份存储库来做到这一点吗？
Our tortoiseSVN repository unfortunately became corrupt today due to a disk glitch.
We have a good working copy based off revision 2897.
Our most recent backup repository is from revision 2848.
We would like to salvage as much as possible of the history, rather than start a new repository.
So, can we do this by committing the working copy directly to the older backup repository ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
如果我没有遗漏任何东西，我在这样的提交中看不到任何问题。只是您不会获得两个修订版之间提交的历史详细信息。
If I am not missing anything, I do not see any problem in such a commit. Only that you will not have history details for the commits between the 2 revisions.
这也发生在我身上 ，我不得不签出一个新的副本，因为当我的本地版本比服务器新时，svn 确实出现了问题。
签出新副本后，将本地文件复制到新副本上（确保不复制 .svn 文件夹），然后提交。您将丢失 2848 年至 2897 年之间的历史记录
This happened to me as well, I had to checkout a fresh copy, as svn got a real hickup when my local version was newer than the server.
When you have checked out a new copy, copy the files from what you had locally over your new copy (make sure you don't copy the .svn folders), and commit. You will loose history between 2848 and 2897
自修订版 2848 起，您已经丢失了提交历史记录。Subversion 工作副本仅保留本地状态......
根据您恢复存储库的方式，您可能还会遇到由于存储库 UUID 不匹配而导致的提交问题。 svn 开关命令可用于指示存储库的更改。另一种选择是使用 tortoiseSVN 创建自修订版 2848 以来的更改补丁，并将其应用于新的结账。
You've lost your commit history, since revision 2848. Subversion working copies only keep local state....
Dependent on how you restore your repository you might also experience commit problems due to a mis-matching repository UUID. The svn switch command can be used to indicate a change of repository. Another option is to use tortoiseSVN to create a patch of the changes since revision 2848 and apply this to a fresh checkout.