From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 08 Mar 2012 06:46:47 GMT
Subject: Re: [ANNOUNCE] Git 1.7.10-rc0
Message-ID: <7vk42vfv3c.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120308063054.GD7643@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Thanks to all other points.

>>  * "git log -G" learned to pay attention to the "-i" option and can
>>    find patch hunks that introduce or remove a string that matches the
>>    given pattern ignoring the case.
>
> This didn't parse well for me. Also, it affects -S, too, doesn't it?
> Maybe:
>
>   * "git log -G" and "git log -S" learned to pay attention to the "-i"
>     option. When "-i" is given, their patterns will match
>     case-insensitively.

I was torn about this item, and indeed my earlier draft read like
yours but I removed "-S" as it felt it was more confusing than it
was worth.  The thing is that -S does not take any pattern --- it is
meant to be given a (typically a multi-line) block of text to find
where the exact block cease to exist in the file.

 * "git log -G" and "git log -S" learned to pay attention to the "-i"
   option.  With "-i", "log -G" finds patch hunks that introduce or
   remove a string that matches the given pattern ignoring the case.
   Similarly with "-i", "log -S" finds where the given block of text
   appears or disappears from the file, but this comparison is done
   case-insensitively.