Jeff King <peff@xxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html