torsdagen den 24 juli 2008 05.34.06 skrev Richie Vos: > I have a project that outputs to a linked directory (for example the > project is in /projects/foo and the project outputs to /projects/bar). > This was causing egit to throw a bunch of "file is not in working > path" errors whenever I rebuilt the project or otherwise interacted > with that linked directory. I tracked it down to GitIndex's add/remove > being called on these files even though these files are not part of > the actual index. > > It seems like egit shouldn't be trying to interact with the index on > these files, and after looking at it, I decided the best solution > would be to realize in the RepositoryMapping that these files do not > point to a repository. I'd be inclined to prefer ignoring any non-plain resource, always. Linked resources are either absolute or relative to a variable. Other than that there is an analogy to symbolic links. Git manages the link, not its content (unless handled elsewhere). The link in this case is in the .project file and thus managed there. EGit could still managed the resource, but not via the link, but rather at the place it is located, iff that happens to be in a project managed by Egit. -- robin -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
