On Sat, Jun 09, 2012 at 11:37:58PM -0700, Junio C Hamano wrote: > Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> writes: > > > On 06/08/2012 04:32 AM, Martin Langhoff wrote: > >> git log -G'regex' is a very usable alternative to the classic > >> pickaxe. Minimal patch to make it usable from gitk. > > > >> set gm [makedroplist .tf.lbar.gdttype gdttype \ > >> [mc "containing:"] \ > >> [mc "touching paths:"] \ > >> - [mc "adding/removing string:"]] > >> + [mc "adding/removing string:"] \ > >> + [mc "changes match regex:"]] > > > > Hi, > > > > this feature is definitely useful. One nitpick: the string that you add > > becomes part of a sentence in the GUI: "prev/next commit changes match > > regex", which is in different grammatical form then the existing > > snippets. Should be something with '-ing'. > > "prev/next commit with changes matching regex" perhaps? There is already the drop-down list to select exact, case-ignoring or regexp matching. I would think that "adding/removing string" combined with "Regexp" matching should select this. What exactly does git log -G do? Paul. -- 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