> IMHO, we should honor ignores in EGit as: > > per-directory .gitignore > per-repostiory GIT_DIR/info/exclude > > per-repository core.excludesfile (yes, really, it can be per > repository, which overrides ~/.gitconfig setting of same) wow. override? really? > > Eclipse global team ignore patterns > so, should these then override, supplement, or something else? the per-repo files (.gitignore's and info/exclude supplement eachother. > Skipping the core.excludesfile in favor of only the Eclipse global > team ignores feels wrong to me, as we may be missing something > the user has configured. FWIW, I think core.excludesfile is a > lot less frequently used then .gitignore and GIT_DIR/info/exclude. > If there is a core.excludesfile, the user is a pretty advanced user > and they really want that behavior to be honored by Git poreclain. > EGit should honor it. I could also argue that an advanced user would expect Egit and git to behave the same. especially for advanced features. and even more so because EGit now is very basic and to be able to use the advanced features you have to switch to the commandline from Eclipse. making this a very very real use-case for EGit usage. Once we have more advanced features implemented this use-case will become less prevalent and only then I'd (personally) be more inclined to allow more behaviour differences -- 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
