Hi, Y.G. noticed that the explanation of '/' handling in the gitignore docs are hard to follow. Worse, it's completely wrong in a number of ways. Here's a series to fix a few of those. Impact: - remove some complete nonsense (how did I mislead myself into thinking patterns without a '/' were anchored?) - address the frequently asked question "how do I un-ignore part of a directory I have ignored?" - relive what seems to be a bug (even when the "foo/" directory is ignored, a "git add foo/bar" should add new changes to the index when that file is already tracked) - some minor clarity improvements At this point, I can hardly trust myself, so careful review for correctness and clarity would be very welcome. Incorporates material from http://thread.gmane.org/gmane.comp.version-control.git/170907/focus=170916 Johannes Sixt (1): Documentation/gitignore: explain how to un-ignore part of a directory Jonathan Nieder (3): Documentation/gitignore: "foo/" patterns match directories, not files under them Documentation: clarify effect of '/' in gitignore(5) patterns Documentation: unanchored gitignore patterns match basename Documentation/gitignore.txt | 48 ++++++++++++++++++++++++++++++------------ 1 files changed, 34 insertions(+), 14 deletions(-) -- 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