git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: marat@seldon.slonopotamus.org
Cc: git@vger.kernel.org
Subject: Re: git check-ignore returns 0 for negated masks
Date: Wed, 20 Nov 2019 12:48:54 +0900	[thread overview]
Message-ID: <xmqqmucrcimx.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191119140135.GA7389@seldon.slonopotamus.org> (marat@seldon.slonopotamus.org's message of "Tue, 19 Nov 2019 17:01:35 +0300")

marat@seldon.slonopotamus.org writes:

> I believe this is a bug because it contradicts check-ignore documentation:
>
>   0 - One or more of the provided paths is ignored.
>   1 - None of the provided paths are ignored.

I think the doc was written with primarily positive entries in mind
(it might even predate the introduction of the feature to allow
negative entries in the file), so it might need to be adjusted with
something like s/be ignored/match the pattern/, perhaps?


      reply	other threads:[~2019-11-20  3:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 14:01 git check-ignore returns 0 for negated masks marat
2019-11-20  3:48 ` Junio C Hamano [this message]

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=xmqqmucrcimx.fsf@gitster-ct.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=marat@seldon.slonopotamus.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 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).