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

Re: [PATCHv2] grep documentation: clarify what files match

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 16, 2010, 02:03 UTC
Message-ID
<7vfx52rl6j.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1266279940-13251-1-git-send-email-lodatom@gmail.com>
Mark Lodato <lodatom@gmail.com> writes:
Show 11 quoted lines
> Clarify that git-grep(1) searches only tracked files, and that each
> <path> is a glob, as in git-add(1).  Add an example to show a simple use
> case for searching all .c and .h files.
>
> The meta-variable <path> should be changed to an official term for
> a path glob, and the description for this should be in git(1), not
> git-add(1).  However, we don't yet have such an official term, so just
> use <path> and reference git-add(1) for now.
>
> Signed-off-by: Mark Lodato <lodatom@gmail.com>
> ---

Looks much better, even though I personally prefer a shorter "work tree" and also think the official name of the stuff is "pathspec".

Will queue until an alternative materializes (if ever) ;-).
Thanks.
Previous: Mark Lodato
Message 5 of 5 in “git-grep ignores untracked files”
  1. Mark LodatoFeb 15, 2010
  2. Junio C HamanoFeb 15, 2010
  3. Mark LodatoFeb 16, 2010
  4. [PATCHv2] grep documentation: clarify what files matchMark Lodato, Feb 16, 2010
  5. Junio C HamanoFeb 16, 2010

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.