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

Re: [PATCH] Correct documentation wording for diff options -S and --pickaxe-all

From
HOHeikki Orsila <shdl@zakalwe.fi>
Date
Aug 31, 2008, 23:59 UTC
Message-ID
<20080831235957.GB16289@zakalwe.fi>
In-Reply-To
<7v63pg3h4o.fsf@gitster.siamese.dyndns.org>
On Sun, Aug 31, 2008 at 04:21:43PM -0700, Junio C Hamano wrote:
Show 20 quoted lines
> Thanks, but if we are doing this, we should reword it to something less
> misleading.  The pickaxe search does not look for changes that contains
> string in the sense people might expect (e.g. "diff -u0 | grep string").
> 
> The machinery looks at the old and new copy, and considers it a match if
> they have different numbers of "string" in them.
> 
> So perhaps something like this
> 
> -S<string>::
> 	Look for differences that changes the number of <string> in the
> 	file.
> 
> --pickaxe-all::
> 	When -S finds a change, show all the changes in that changeset,
>         not just the files for which the number of <string> in them
> 	changes.
> 
> but I am bad at writing, so I'll ask others to come up with a better
> wording.
Perhaps like this:

-S: "Look for differences that change the number of <string> matches in a file. In other words, moving the <string> inside a file does not imply a match, but adding or removing <string> will."

-- 
Heikki Orsila
heikki.orsila@iki.fi
http://www.iki.fi/shd
Previous: Junio C Hamano
Message 3 of 3 in “Correct documentation wording for diff options -S and --pickaxe-all”
  1. Correct documentation wording for diff options -S and --pickaxe-allHeikki Orsila, Aug 31, 2008
  2. Junio C HamanoAug 31, 2008
  3. Heikki OrsilaAug 31, 2008

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.