VisualSVN 如何回滚修订号?

发布于 2024-09-01 09:25:38 字数 479 浏览 10 评论 0原文

我工作的公司遭遇了严重的服务器故障。在此故障期间,SVN 存储库丢失。但仍有希望! 我们有一个存储库的旧备份,我已经使用 VisualSVN 成功恢复了它。

我现在面临的问题是我无法更新/提交失败前签出文件夹。造成此问题的原因是,例如:本地文件夹的修订号为 2361,而存储库本身的修订号为 2290,这是较旧的。

有办法解决这个问题吗?我可以如何更改本地副本或服务器副本上的修订号吗?

几点:

  • 我使用的是TortoiseSVN 1.6.6。
  • 我可以从存储库中签出文件夹并且连接处于活动状态。
  • 我选择了一个文件夹并对其使用了重新定位选项。这帮助我发现修订号有问题,
  • 我已经尝试了一些合并选项,但这让我现在变得特别。 (我愿意接受建议)

谢谢你的宝贵时间,

Ita

The company I work in has suffered a major server failure. During this failure the SVN Repository was lost. But there is still hope !
We have an old backup of the repository which I've managed to successfully restore using VisualSVN.

The problem I'm facing now is that I can't update / commit pre-failure checkedout folders. The reason for this problem is that for instance: a local folder has a revision number of 2361, while the repository itself holds a revision number of 2290, which is older.

Is there a way to deal with this issue ? Can I some how change the revision numbers on either the local copy or the server copy?

A few points:

  • I'm using TortoiseSVN 1.6.6.
  • I can checkout folders from the repo and the connection is active.
  • I've picked one of my folders and used the Relocate option on it. This helped me see that there is something wrong with the revision number
  • I've experimented a bit with the merge option but this lead me now where special. (I'm open for suggestions )

Thank you for your time,

Ita

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

臻嫒无言 2024-09-08 09:25:38

您需要将项目检出到新的工作副本中,然后使用所需的任何工具将更改移至新的工作副本中。

您根本无法退回修订号。您当前的工作副本可能包含存储库旧备份中没有的更改,并且工作副本不会将它们视为“与存储库不同”。

由于您的存储库丢失了,因此协调当前工作副本的机会也随之消失。

You'll need to checkout your project into a new working copy, then use whatever tools that you have to move the changes into the new working copy.

You simply can't turn back the revision number. Your current working copy potentially contains changes that aren't in the older backup of the repository, and the working copy doesn't treat them as 'different from the repository'.

As your repository was lost, so was any chance of reconciling your current working copy.

难忘№最初的完美 2024-09-08 09:25:38

将恢复的备份的最新版本检出到工作副本中。对旧工作副本进行 svn 导出,然后将所有文件/文件夹复制到之前签出的工作副本上。如果需要的话,可以添加一个 svn add 并提交。这应该总结所有更改。

Checkout the newest revision of the restored backup into a working copy. do an svn export of and old working copy and simply copy all files/folders onto the previously checkout working copy. Than do an svn add if needed and commit. This should summ all changes.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文