From: Charles Bailey <charles@hashpling.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: What's cooking in git.git (Jul 2016, #02; Wed, 6)
Date: Thu, 7 Jul 2016 21:40:02 +0100 [thread overview]
Message-ID: <20160707204002.GA19138@hashpling.org> (raw)
In-Reply-To: <xmqqr3b6qwdt.fsf@gitster.mtv.corp.google.com>
On Wed, Jul 06, 2016 at 02:39:26PM -0700, Junio C Hamano wrote:
> * nd/ita-cleanup (2016-07-01) 3 commits
> (merged to 'next' on 2016-07-06 at f15aeba)
> + grep: fix grepping for "intent to add" files
> + t7810-grep.sh: fix a whitespace inconsistency
> + t7810-grep.sh: fix duplicated test name
>
> Git does not know what the contents in the index should be for a
> path added with "git add -N" yet, so "git grep --cached" should not
> show hits (or show lack of hits, with -L) in such a path. But we
> did by mistake, which has been corrected.
>
> Will merge to 'master'.
I just wanted to clarify what was actually fixed. The actual bug that
was reported and fixed was the fact that 'git grep' (without --cached)
wasn't searching the contents of files in the working tree if the index
entry had the "intent to add" bit set.
My original proposed fix (reversion of the commit that introduced this
change) caused the re-introduction of behaviour where "i-to-a" files
would be reported with -L --cached which wasn't desired. I think because
we spent most of our energy and discussion on fixing this in a better
way we've lost the intent of the original patch.
next prev parent reply other threads:[~2016-07-07 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 21:39 What's cooking in git.git (Jul 2016, #02; Wed, 6) Junio C Hamano
2016-07-07 20:40 ` Charles Bailey [this message]
2016-07-07 21:21 ` Junio C Hamano
2016-07-07 21:34 ` Charles Bailey
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=20160707204002.GA19138@hashpling.org \
--to=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).