ankhsvn：存储库在内部折叠
我一直在使用 AnkhSVN 和 VS2010 来开发多个项目（“解决方案”）。有一段时间我的承诺进展顺利。但最近，Ankhsvn 将我的存储库更改为我的项目之一，因此本应是子项目的项目现在复制了整个存储库结构。这种情况发生过多次，以至于我必须检查的当前项目位于另一个项目中，而另一个项目本身又位于另一个项目中。我已经转到文件 ->颠覆->更改源代码管理但无法编辑 URL。当我尝试使用“挂起的更改”时，我收到一条有关工作副本上的锁损坏的 errmsg。当然我已经尝试过几次 Clean 了。我也尝试过 Switch，我认为这给我带来了更多麻烦。回购协议最初是如何改变的？知道我做错了什么（以及如何解决）吗？
I've been using AnkhSVN with VS2010 for development of several projects ("solutions"). For a while my commits have been going fine. But recently, Ankhsvn has changed my repository to one of my projects, so that what should be a child project now duplicates the entire repository structure. This has happened on more that one occasion such that the current project I have to check out is located within another project which itself is within another project. I've gone to File -> Subversion -> Change Source Control but the URL can't be edited. When I try using Pending Changes, I get an errmsg about a broken lock on the working copy. Of course I have tried Clean several times. I also tried Switch which I think got me into more trouble. How did the repo get changed in the first place? Any idea what I did wrong (and how to fix) ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
可能发生的情况是绑定路径已更改。您可以通过选择“文件”->“文件”中的解决方案来更改此设置。颠覆->更改源代码管理，然后单击
...按钮。该值存储在 sln 文件的 SCC Bindings 部分中。使用 File -> 查看解决方案时会发生什么？打开-> Subversion 项目的特点是它在上面的 SCC 绑定路径定义的级别上进行检查。
我还建议查看较小的工作副本，因为这样效率更高。您希望在主干级别（或当然任何分支）进行检查。检查上面的分支意味着分支和标记突然变得昂贵（因为每次发生它时你的工作副本都会增长很多）
What probably happen is that the binding path was changed. You can change this by selecting the solution in File -> Subversion -> Change Source Control, and clicking the
...button. This value is stored in the sln file in the SCC Bindings section.What happens when checking out the solution, using File -> Open -> Subversion Project, is that it checks out at the level defined by the SCC Binding Path above.
I would also recommend checking out a smaller working copy, because it's much more efficient that way. You're looking to check out at the trunk level (or any branch ofcourse). Checking out above branch means that branching and tagging is suddenly expensive (because each time it happens your working copy grows a lot)