From: Elazar Leibovich Date: Wed, 25 May 2011 11:28:12 GMT Subject: Re: Supporting "-v" option for git-log Message-ID: In-Reply-To: On Wed, May 25, 2011 at 2:21 PM, Tim Mazid wrote: > > Well, personally, I've never used the --grep option. I pipe it through > grep, where I can supply options such as -v. But then you must use single-line commits output. Which is inconvenient if you want to read all the commit message. > 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"? Now that I think of it, we already have the '--not' option for revision specifiers. Why won't we use it for grep patterns? That way -v will not be overloaded (it usually means verbose). For example git log --all --not --grep A --grep B Would mean find all commits without A and with B, in SQL "SELECT * FROM COMMITS WHERE message NOT LIKE '%A%' AND message LIKE '%B%'".