Hi,
Ph. Marek wrote:
> Gitk offers to search in commits "adding/removing string:" "exact"; this
> works,
> I can search for eg. function names, and the corresponding commits are
> highlighted.
>
> Now, changing the match type field to "Regexp" works for simple function names
> (consisting of [a-zA-Z]) too; but as soon as I want to _use_ regex features
> (eg. ".*"), no match is found anymore.
Looks like a documentation bug. :) What "adding/removing string" does
is, for each diff, to count the number of matches before and after the
change and consider this a hit if they differ. The purpose is to find
out when some mysterious piece of code first came into being, for
example to find out when a particular function was introduced:
git log -S 'foo *[(].*[)]' --pickaxe-regex
What you might have been looking for is rather a "grep diff" search,
which would look for commits that touched lines matching a particular
regex. This should be doable for anyone interested in hacking gitk
--- it amounts to plumbing the UI to offer a chance to use the option
-G in the same places where it can currently use -S. See
http://bugs.debian.org/589283 for details.
The git-log(1) manual explains this a little better. Unfortunately I
don't think there's a gitk manual to explain it.
Thanks for your interest and hope that helps,
Jonathan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
