移动的符号链接从 Windows 资源管理器中消失
我想先更改 ClearCase 内源代码的结构,然后再使用自定义脚本将其导出到另一个 SCM 系统。由于原始代码可能仍会略有变化,因此我通过将现有文件夹的内容符号链接到新结构中来实现此目的。
现在所需的文件夹结构已更改,我需要移动这些符号链接(或重新开始整个过程,如果没有人可以帮助我,这是我的后备策略)。但是在移动任何符号链接后(顺便说一下,在动态视图中的同一 VOB 内),Windows 资源管理器不会在新位置显示元素。 ClearCase Explorer 确实按预期在新位置显示它们并标记为符号链接;但他们似乎失去了目标,因为上下文菜单中的“扭曲到目标”选项呈灰色。
重新启动 PC 并卸载/重新安装 VOB 都无法改善情况。
谁能告诉我这种情况是如何发生的,如何防止这种情况再次发生,以及如何恢复看似损坏的链接?
I'd like to change the structure of our source code inside ClearCase before using a custom script to export that to another SCM system. As the original code may still change slightly, I did this by symlinking the contents of the existing folders into the new structure.
Now the desired folder structure has changed and I need to move those symlinks (or start the whole process over, which is my fall-back strategy if no one can help me here). But after moving any symlinks (inside the same VOB in a dynamic view by the way), Windows Explorer does not show the elements at the new position. ClearCase Explorer does show them as expected, in the new location and tagged as a symbolic link; but they appearantly lost their target, as the option "Warp to target" in the context menu is greyed out.
Restarting the PC and un-/remounting the VOB all did nothing to better the situaton.
Can anyone tell me how this could happen, how to prevent this from happening again and possibly how I can restore the appearantly broken links?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
如果目标本身已更改,则看起来比 VOB 符号链接 失去其目标,并且“扭曲到符号链接目标”上下文菜单不起作用。
检查您的符号链接(此处使用 在动态视图中)是软链接。
但是,如果移动链接并且其目标发生变化,我认为删除并重新创建符号链接会更快。
实际上,OP SvenS 在评论中提到:
If the target has itself changed, it seems normal than the VOB symlinks loses their target, and that the "Warp to Symlink Target" contextual menu doesn't work.
Check that your symlink (used here in a dynamic view) is a soft link.
But if move the link and its target change, I think it is quicker to remove and recreate the symlink.
Actually, the OP SvenS mentions in the comments: