public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Michael J Gruber <git@drmicha•warpmail.net>
Cc: git@vger•kernel.org, Guilherme <guibufolo@gmail•com>
Subject: Re: [PATCH] check-ignore: clarify treatment of tracked files
Date: Thu, 04 Dec 2014 12:15:41 -0800	[thread overview]
Message-ID: <xmqqzjb3rx1u.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <fbc5799c32357e8bff0c690ba7bc4cd46374684d.1417706481.git.git@drmicha.warpmail.net> (Michael J. Gruber's message of "Thu, 4 Dec 2014 16:23:05 +0100")

Michael J Gruber <git@drmicha•warpmail.net> 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@gmail•com>
> Signed-off-by: Michael J Gruber <git@drmicha•warpmail.net>
> ---
> 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::

next prev parent reply	other threads:[~2014-12-04 20:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  9:06 git add <single file> and git add <list of files> behave differentely for ignored files Guilherme
2014-12-04 11:11 ` Konstantin Khomoutov
2014-12-04 11:49   ` Guilherme
2014-12-04 15:02 ` Michael J Gruber
2014-12-04 15:23   ` [PATCH] check-ignore: clarify treatment of tracked files Michael J Gruber
2014-12-04 20:15     ` Junio C Hamano [this message]
2014-12-08 16:13       ` Michael J Gruber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqzjb3rx1u.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@drmicha$(echo .)warpmail.net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=guibufolo@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox