如果不升级新的 Tortoise 1.7 就无法更新
我已经下载了 TortoiseSVN-1.7.0.22068-x64-svn-1.7.0.msi
,现在无法更新项目文件夹或提交任何项目文件。
有了这个新版本,Tortoise 开发人员现在迫使我们升级该文件夹才能使用它。但它会失去向后兼容性:旧的乌龟客户端无法与升级的文件夹交互。
这是正确的吗?
我们都必须在公司升级我们的 Tortoise 客户端,或者等待下一个 Tortoise 版本的向后兼容功能?
I have downloaded TortoiseSVN-1.7.0.22068-x64-svn-1.7.0.msi
and now it is impossible to update a project folder or commit any project files.
With this new version, Tortoise developers now are forcing us to upgrade the folder in order to use it. But it would loose backward compatibility: old tortoise clients cannot interact with the upgraded folder.
Is this correct?
We all have to upgrade our Tortoise clients in company or maybe wait for a backward compatibility feature on next Tortoise version?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(3)
是的,WC 必须升级到 1.7。是的,由于实施 WC-NG,1.6 和 1.7 客户端在 WC 处理中不兼容。
不。每个人都可以离开 1.6 TSVN 并继续使用 1.6 工作副本。 Server-version同时可以是任意版本
Yes, WCs must be upgraded to 1.7. Yes, 1.6 and 1.7 clients are uncompatible in the WC-handling, due to implementing WC-NG.
No. Everybody can leave 1.6 TSVN and continue to use 1.6 working copies. Server-version at the same time can be any version
并不是每个人都必须立即升级。实际上,我在笔记本电脑上运行 tortoise svn 1.7 版,在台式机上运行旧版本。它仍然适用于远程存储库。然而,它所讨论的其他 svn 客户端是同一台机器上的客户端。换句话说,我还必须将 SlikSvn 和 Visual SVN 升级到 1.7。
Not everyone has to upgrade at once. I am actually running tortoise svn version 1.7 on my laptop and an older version on my desktop. It still works with the remote repository. However the other svn clients that it is talking about are those on the same machine. In other words, I also had to upgrade my SlikSvn to 1.7 and also Visual SVN too.
是的,旧客户端可能无法使用升级到 SVN 1.7 的工作副本。请注意,TortoiseSVN 只是强制您确认工作副本的升级;以前版本的 TortoiseSVN 只会将您的工作副本升级到最新的 SVN 格式,而不会与您核实。
有关更多详细信息,请参阅“升级工作副本”部分下的发行说明。
Yes, older clients will probably not work with working copies upgraded to SVN 1.7. Note that TortoiseSVN is just forcing you to acknowledge the upgrade of your working copy; previous versions of TortoiseSVN would just upgrade your working copy to the latest SVN format without checking with you.
See the release notes for more details, under the section "Upgrading the Working Copy".