> From: timmazid@xxxxxxxxxxx > > From: elazarl@xxxxxxxxx > > Oops, let me be 100% clear about that, "git log -v > > --grep==> presented a possible syntax. > > > > $ git --version > > git version 1.7.4.msysgit.0 > > $ git log -v --grep=Normalized > > commit 88c7a82aaf240ed130c64c455c294e7af04d30f8 > > Author: Elazar > > Date: Mon May 16 10:40:21 2011 +0300 > > > > Normalized Makfile so that it'll work by default. Include Makefile > > > > see, it ignores the "-v", and include only commits with "Normalized" - > > the ones I don't want to see. > > Ah, I see; my apologies. > > Well, personally, I've never used the --grep option. I pipe it through > grep, where I can supply options such as -v. However, if the --grep > option already exists, then it does make sense to allow users to use > options they would normally be able to with grep. > > As for the syntax, that seems like a good idea on the surface, but > how would you go about supporting other grep options? Such as > "-i"? Woops; my bad; "-i" is already supported. But the point still stands... I think? Should there be a seperate "--grep-options" option for "git log" to pass options onto grep? Tim. () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- 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