移动文件夹和在SVN中移动的后果有什么后果？
我们意外地在SVN存储库中移动了一个主要的文件夹，历史悠久。之所以发生，是因为我们选择了“移动和重命名”，而不是“复制和重命名”来偶然地创建一个新的分支。该操作以这样的方式显示在龟中：
| 路径 | 动作 | 副本，来自路径 | / |
|---|---|---|---|
| 分支/功能/nameOffeAtureBranch | 添加 | /trunk/thefolder/thefolder | 10000 |
| /trunk/thefolder | 随后删除 |
，添加了文件夹：返回文件夹：
| 路径 | 动作 | 副本，从路径 | / |
|---|---|---|---|
| trunk/thefolder | 中添加。添加 | /分支/功能/nameOffeAturebranch | 10001 |
历史记录（例如，指责）仍然存在，但是如果启用了“停止复制/重命名”，则乌龟SVN停止查看有问题的修订版。我们可以忍受。主要的问题是：我们还不知道其他后果吗？还有：还有其他建议吗？
We accidentally moved a major folder in our SVN repository with a long history. It happened because we selected "move and rename" instead of "copy and rename" to create a new branch by accident. The operation shows up in TortoiseSVN like this:
| Path | Action | Copy from Path | Revision |
|---|---|---|---|
| /branches/feature/NameOfFeatureBranch | Added | /trunk/TheFolder | 10000 |
| /trunk/TheFolder | Deleted |
Afterwards, the folder was added back:
| Path | Action | Copy from Path | Revision |
|---|---|---|---|
| /trunk/TheFolder | Added | /branches/feature/NameOfFeatureBranch | 10001 |
The history (e.g. in a blame) is still all there, but Tortoise SVN stops looking past the problematic revision if "Stop on copy/rename" is enabled. We can live with that. The main question is: Are there any other consequences that we are not yet aware of? Also: Any other suggestions?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
只是让任何人都知道谁遇到了这个问题：经过几周与所描述的状态合作之后，我们找不到任何问题（除了我们需要取消选择“停止在Tortoise SVN中的复制/重命名”的小麻烦之外）。请注意，我们有一个非常复杂的构建系统，有几个人也使用git-svn。尽管如此，到目前为止还没有问题。
Just to let anyone know who comes across this issue: After several weeks of working with the described state, we could not find any issues (besides the minor nuisance that we need to deselect "Stop on copy/rename" in Tortoise SVN). Note that we have a quite complex build system and several people also use git-svn. Still, no problems so far.