From: Johannes Altmanninger <aclopte@gmail.com>
To: gitster@pobox.com
Cc: aclopte@gmail.com, git@vger.kernel.org
Subject: Re: Unexpected behavior on diff -I<regex> --name-only
Date: Thu, 17 Dec 2020 00:18:39 +0100 [thread overview]
Message-ID: <20201216231840.3163806-1-aclopte@gmail.com> (raw)
In-Reply-To: <xmqqeejsdv7x.fsf@gitster.c.googlers.com>
On Mon, Dec 14, 2020 at 11:49:06AM -0800, Junio C Hamano wrote:
> This is not a new issue limited to -I at all. If you did this:
Right, I didn't think of -w at all!
> I do not offhand remember if -I flips diff_from_contents
> bit, but I wouldn't be surprised if the recent change added the
> support for -I forgot to do so.
Spot on ;)
next prev parent reply other threads:[~2020-12-16 23:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 19:00 Unexpected behavior on diff -I<regex> --name-only Johannes Altmanninger
2020-12-14 19:49 ` Junio C Hamano
2020-12-16 23:18 ` Johannes Altmanninger [this message]
2020-12-16 23:18 ` [PATCH] diff: suppress --name-only paths where all hunks are ignored Johannes Altmanninger
2020-12-17 1:27 ` Re* " Junio C Hamano
2020-12-20 22:34 ` Johannes Altmanninger
2020-12-21 19:29 ` 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=20201216231840.3163806-1-aclopte@gmail.com \
--to=aclopte@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).