From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Pauli Virtanen <pav@iki.fi>, git@vger.kernel.org
Subject: Re: [PATCH] git-add--interactive: never skip files included in index
Date: Sun, 11 Oct 2009 15:22:05 -0700 [thread overview]
Message-ID: <7vpr8tr2pe.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 20091011191440.GA2532@coredump.intra.peff.net
Jeff King <peff@peff.net> writes:
> On Sun, Oct 11, 2009 at 11:52:10AM -0700, Junio C Hamano wrote:
>
>> Thanks.
>>
>> The change looks innocent enough and I do not expect to see any unexpected
>> regressions from it, but it is a bit too late for 1.6.5 cycle, so let's
>> queue this fix and aim for 1.6.5.1.
>
> I think this patch is good to apply, as there is no conceivable reason
> to even look at excludes when listing modified files.
>
> But this triggered my spider sense; shouldn't --exclude-standard simply
> be a no-op for ls-files when we are not listing untracked files? And
> bisecting, it seems that it is a very old regression caused by 63d285c
> (per-directory-exclude: lazily read .gitignore files, 2007-11-29).
>
> I don't know if it is worth fixing now or not. It does seem a bit
> inconsistent to me (since everything else is very clear that .gitignore
> is only about untracked files), but nobody seems to have been
> complaining for the last two years (and they may have, in fact, been
> coding to the new behavior).
This is one of those moments when I feel very blessed to have competent
and diligent people around me ;-)
I think you are right; that we shouldn't filter the output with gitignore
entries when showing what is _in_ the index.
next prev parent reply other threads:[~2009-10-11 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 15:51 [PATCH] git-add--interactive: never skip files included in index Pauli Virtanen
2009-10-11 18:52 ` Junio C Hamano
2009-10-11 19:14 ` Jeff King
2009-10-11 22:22 ` Junio C Hamano [this message]
2009-10-12 1:40 ` Jeff King
2009-10-12 2:46 ` Junio C Hamano
2009-10-12 5:11 ` Jeff King
2009-10-12 23:42 ` Junio C Hamano
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=7vpr8tr2pe.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pav@iki.fi \
--cc=peff@peff.net \
/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.