git pickaxe - more confusion

2 messages, 1 author, 2016-06-15 · open the first message on its own page

git pickaxe - more confusion

From: Martin Langhoff <hidden>
Date: 2016-06-15 22:43:05

Call me blunt, I cannot figure out how to use git pickaxe on a subdir.
As it's aliased to blame it really wants a file, but I have a couple
of top-level directories I want it to scan for a constant.

In short,

     git pickaxe -L '/CURLOPT_SSL/' origin/cvshead -- mnet lib/mnet

doesn't want to play with me. I initially tried with -S but the new
way of doing it is -L, it seems -- passing the regex where the line
numbers should be ;-)

cheers,



martin

Re: git pickaxe - more confusion

From: Martin Langhoff <hidden>
Date: 2016-06-15 22:43:05

On 4/18/07, Martin Langhoff [off-list ref] wrote:
In short,

     git pickaxe -L '/CURLOPT_SSL/' origin/cvshead -- mnet lib/mnet

doesn't want to play with me. I initially tried with -S but the new
And I was trying the new pickaxe because oldstyle git-whatchanged was
messing up with my head because the space after the -S parameter is
not valid syntax.

Doesn't work:
        git whatchanged -p -S 'CURLOPT_' cvshead -- mnet lib/mnet

Works:
        git whatchanged -p -S'CURLOPT_' cvshead -- mnet lib/mnet

So -- I'm sorted with this but it's not actually described anywhere I
can see :-/ -- I only realised that reading Linus' old posts showing
off pickaxe there was no space after the -S and gave it a go.

Weird semantics!


martin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help