git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Something wrong with pickaxe?

From
Andreas Ericsson <ae@op5.se>
Date
Jan 19, 2006, 09:12 UTC
Message-ID
<43CF5816.1010004@op5.se>
In-Reply-To
<7v3bjlt66q.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
Show 10 quoted lines
> Linus Torvalds <torvalds@osdl.org> writes:
> 
>>... Junio would be open to 
>>more friendly pickaxe semantics if the suggested semantics change was 
>>accompanied by an actual diff to implement them.
> 
> 
> True again.  It is hard to be "more friendly" without actually
> generating a diff ;-).
> 

I thought generating diffs was fairly cheap. I agree with Linus somewhat though. I've been puzzled more than once with the pickaxe behaviour when I give it a function name to search for and want to know when the calling semantics changed for that function. I usually also end up doing a whatchanged -p and search it.

It would be neat if the current behaviour could be kept with --pickaxe-exact but all commits containing changes to lines matching the string was returned by default. Or possibly --pickaxe-thourough to do the other way around.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231
Previous: Junio C HamanoNext: Junio C Hamano
Message 4 of 9 in “Something wrong with pickaxe?”
  1. Johannes SchindelinJan 18, 2006
  2. Linus TorvaldsJan 18, 2006
  3. Junio C HamanoJan 19, 2006
  4. Andreas EricssonJan 19, 2006
  5. Junio C HamanoJan 19, 2006
  6. Andreas EricssonJan 19, 2006
  7. Junio C HamanoJan 19, 2006
  8. Linus TorvaldsJan 19, 2006
  9. Junio C HamanoJan 19, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.