From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: git <git@vger.kernel.org>
Subject: Re: [PATCH] check-ignore: correct documentation about output
Date: Mon, 16 Nov 2015 15:13:04 +0100 [thread overview]
Message-ID: <1447683184.2733.0.camel@kaarsemaker.net> (raw)
In-Reply-To: <20151108201036.GA28434@spirit>
Ping.
On zo, 2015-11-08 at 21:10 +0100, Dennis Kaarsemaker wrote:
> By default git check-ignore shows only the filenames that will be
> ignored, not the pattern that causes their exclusion.
>
> Signed-off-by: Dennis Kaarsemaker <dennis@kaarsemaker.net>
> ---
> Documentation/git-check-ignore.txt | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/git-check-ignore.txt b/Documentation/git
> -check-ignore.txt
> index 59531ab..0a628ac 100644
> --- a/Documentation/git-check-ignore.txt
> +++ b/Documentation/git-check-ignore.txt
> @@ -16,10 +16,9 @@ DESCRIPTION
> -----------
>
> For each pathname given via the command-line or from a file via
> -`--stdin`, show the pattern from .gitignore (or other input files to
> -the exclude mechanism) that decides if the pathname is excluded or
> -included. Later patterns within a file take precedence over earlier
> -ones.
> +`--stdin`, check whether the file is excluded by .gitignore (or
> other
> +input files to the exclude mechanism) and output the path if it is
> +excluded.
>
> By default, tracked files are not shown at all since they are not
> subject to exclude rules; but see `--no-index'.
> --
> 2.6.3-495-gf0a7f49
>
>
--
Dennis Kaarsemaker
http://www.kaarsemaker.net
next prev parent reply other threads:[~2015-11-16 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-08 20:10 [PATCH] check-ignore: correct documentation about output Dennis Kaarsemaker
2015-11-16 14:13 ` Dennis Kaarsemaker [this message]
2015-11-17 0:22 ` Stefan Beller
2015-11-17 22:37 ` Jeff King
2015-11-20 11:31 ` Jeff King
2015-11-20 20:29 ` Dennis Kaarsemaker
2015-11-20 20:30 ` [PATCH v2] " Dennis Kaarsemaker
2015-11-24 22:13 ` Jeff King
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=1447683184.2733.0.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.