为什么我在完全同步的目录上看到 SVN 的未提交更改装饰器？
我正在使用 Subclipse 访问 Subversion 存储库。 MyEclipse 的“Package Explorer”窗口中的某些文件夹显示有未提交的更改装饰器： 
通常，这意味着我的计算机上的目录中的一个或多个文件具有本地未提交的更改。但现在，某些文件夹似乎不包含未提交更改的文件或子文件夹。 （即，我没有看到以下任何一个： 
）
团队同步模式支持这种不一致。当我告诉 Subclipse 与受影响目录之一的存储库同步时，我看到以下屏幕：
的文件夹下都会有一个与其存储库对应项不匹配的列表。然而，正如您所看到的，除了文件夹本身的“将被提交”装饰器之外，什么也没有。 “SVN 更新”和“替换为存储库版本”命令不执行任何操作，“与存储库版本比较”会弹出“未发现更改”对话框。
简而言之，似乎我的一些目录被标记为具有未提交的更改，即使它们没有。为什么会发生这种情况，我该如何解决它？
（图标装饰器名称和描述部分取自 这个答案对我之前的一个问题。）
I'm accessing a Subversion repository with Subclipse. Some of the folders in the Package Explorer window of MyEclipse show up with the uncommitted changes decorator:
Usually, this means that one or more files in the directory on my machine have local, uncommitted changes. Right now, though, some of the folders appear to contain no files or subfolders with uncommitted changes. (I.e. I don't see any of these: )
This inconsistency is supported by Team Synchronization mode. When I tell Subclipse to synchronize with the repository for one of the affected directories, I see the following screen:
Under normal conditions, there would be a list under the folder of every file that didn't match its repository counterpart. However, as you can see, there's nothing there but a "will be committed" decorator on the folder itself. The "SVN update" and "replace with repository version" commands do nothing, and "compare with repository version" brings up a "no changes found" dialog.
In short, it seems as though some of my directories are getting marked as having uncommitted changes even though they don't. Why is this happening, and how can I resolve it?
(Icon decorator names and descriptions taken in part from this answer to one of my earlier questions.)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
当涉及 IDE 和图形工具时，我通常从良好的 ole 命令行客户端执行健全性检查。如果可以的话，打开终端并运行“svn status”来查看 Subversion 认为工作副本的状态。至于可能发生这种情况的有效位置是版本化属性、不同步的项目/文件系统以及在 MyEclipse 外部进行的更改。
When it comes to IDEs and graphical tools, I typically perform a sanity check from the good ole command line client. If you can, open a terminal and run "svn status" to see what Subversion thinks the state of the working copy is. As for valid places where this can happen are versioned properties, out of sync project/filesystem and changes made outside of MyEclipse.
我遵循了 Jeremy Whitlock 在他的回答中给出的建议，并在受影响的目录上运行了 svn status 。以下是结果，供将来遇到此问题的任何人使用：
其他受影响的目录也有同样的问题。至于如何解决它，
我会问一个单独的问题，然后用链接更新此答案我已经问了一个单独的问题这里。I followed the advice Jeremy Whitlock gave in his answer and ran
svn statuson the affected directories. Here are the results, for anyone who has this problem in the future:The other affected directories had the same issue. As for how to resolve it,
I'll ask a separate question and then update this answer with a linkI've asked a separate question here.