Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> writes: > By default, check-ignore does not list tracked files at all since > they are not subject to ignore patterns. > > Make this clearer in the man page. > > Reported-by: Guilherme <guibufolo@xxxxxxxxx> > Signed-off-by: Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> > --- > That really is a bit confusing. Does this help? Thanks. "git check-ignore" is a tool to debug your .gitignore settings when your expectation does not match the reality, so having this new sentence here is a good thing to do, but I wonder if there is a more prominent and central place where people learn about the ignore mechanism the first place. If we had this sentence there, too, that may reduce the need to debug their .gitignore settings in the first place. Perhaps Documentation/gitignore.txt? Documentation/user-manual.txt? > > Documentation/git-check-ignore.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/git-check-ignore.txt b/Documentation/git-check-ignore.txt > index ee2e091..788a011 100644 > --- a/Documentation/git-check-ignore.txt > +++ b/Documentation/git-check-ignore.txt > @@ -21,6 +21,9 @@ the exclude mechanism) that decides if the pathname is excluded or > included. Later patterns within a file take precedence over earlier > ones. > > +By default, tracked files are not shown at all since they are not > +subject to exclude rules; but see `--no-index'. > + > OPTIONS > ------- > -q, --quiet:: -- 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