Leila Muhtasib <muhtasib@xxxxxxxxx> writes: > git-status now lists empty directories under the untracked header. Before this > modification, git status did not list empty directories. The header changed > from 'Untracked files' to instead display 'Untracked files and directories'. > A helpful reminder is also added after empty directories indicating they cannot > be added/staged if they are empty. git status -u is unchanged, and will still > only show untracked files just as before. As a result, no need for > documentation change. Please do not write a thick wall of text like this. State the problem you are trying to solve first, by describing the current behaviour you want to highlight, and explain why you think the current behaviour is bad. Then describe how you propose to solve that issue in a separate paragraph. For example: > git-status now lists empty directories under the untracked header. Before this > modification, git status did not list empty directories. The above is backwards. "git status" lists untracked files and directories full of untracked files, but does not list empty directories. This is bad for such and such reasons. Then describe your solution (which should be a short two sentence in this case, because in the problem description you would have justified adding "empty directories" section). Show empty directories to the "Untracked" section as well. Because an empty directory by definition does not have anything that the user could add, suggest the user to create a file to be committed and then add it. Having said all that, I personally doubt this is a useful change. I may thought of adding a README file to a relatively new project that does not yet have one while in shower but I haven't even created the file in the working tree. And I forget about it once I get to the office. Should the system remind me to create README and then add? Your patch would not give me such a reminder once the top-level directory is populated (because it is no longer empty). Even if I were planning to add Documentation/README instead, I would get such a reminder only if the Documentation directory is empty. Once the directory is populated, I wouldn't get "create README and then add". Why should an empty directory so special? -- 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