From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Elijah Newren via GitGitGadget <gitgitgadget@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] check-ignore: fix handling with negated patterns
Date: Wed, 19 Feb 2020 13:36:39 -0800 [thread overview]
Message-ID: <xmqq7e0idztk.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BHaTK62W4_rUaJXNUPSfu9cBD5MrmjgbJeMuA+7s3+rGg@mail.gmail.com> (Elijah Newren's message of "Mon, 17 Feb 2020 13:07:46 -0800")
Elijah Newren <newren@gmail.com> writes:
> No, it is not more like that; the check-ignore manpage currently claims this:
>
> For each pathname given via the command-line or from a file via
> --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.
Thanks. I wasn't paying attention to what happened to the manpage
(or to the command for that matter) after I wrote it as a debugging
aid X-<.
The updated version looked reasonable to me. Thanks.
next prev parent reply other threads:[~2020-02-19 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:15 [PATCH] check-ignore: fix handling with negated patterns Elijah Newren via GitGitGadget
2020-02-17 18:04 ` Junio C Hamano
2020-02-17 18:41 ` Elijah Newren
2020-02-17 20:41 ` Junio C Hamano
2020-02-17 21:07 ` Elijah Newren
2020-02-19 21:36 ` Junio C Hamano [this message]
2020-02-18 20:36 ` [PATCH v2] check-ignore: fix documentation and implementation to match Elijah Newren via GitGitGadget
2020-02-18 21:27 ` Junio C Hamano
2020-02-18 23:05 ` [PATCH v3] " Elijah Newren via GitGitGadget
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=xmqq7e0idztk.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=newren@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).