From: Johannes Sixt <j.sixt@viscovery.net>
To: Dave Williams <dave@opensourcesolutions.co.uk>
Cc: git@vger.kernel.org, Adam Spiers <git@adamspiers.org>
Subject: Re: [PATCH] check-ignore: Add option to ignore index contents
Date: Fri, 30 Aug 2013 08:51:34 +0200 [thread overview]
Message-ID: <522040F6.5060602@viscovery.net> (raw)
In-Reply-To: <20130829224652.GA13621@opensourcesolutions.co.uk>
Am 8/30/2013 0:46, schrieb Dave Williams:
> +-i, --ignore-index::
> + Don't look in the index when undertaking the checks. This means
> + the results deviate from those seen by git add and git status
> + but is useful when understanding why a path became tracked by
> + e.g. git add . and was not ignored as expected by the rules.
Did you mean to say "was not ignored as expected by the user"? Because the
"the rules" cannot "expect" something, they only "are applied".
-- Hannes
prev parent reply other threads:[~2013-08-30 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 22:46 [PATCH] check-ignore: Add option to ignore index contents Dave Williams
2013-08-30 0:10 ` Adam Spiers
2013-08-30 0:51 ` Duy Nguyen
2013-08-30 4:13 ` Junio C Hamano
2013-08-30 0:57 ` Junio C Hamano
2013-08-30 6:51 ` Johannes Sixt [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=522040F6.5060602@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=dave@opensourcesolutions.co.uk \
--cc=git@adamspiers.org \
--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 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).