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

Re: [BUG/PATCH] git grep shows the same hit repeatedly for unmerged paths

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Dec 6, 2007, 07:29 UTC
Message-ID
<4757A4DD.901@viscovery.net>
In-Reply-To
<7vsl2gk7e3.fsf@gitster.siamese.dyndns.org>
Junio C Hamano schrieb:
Show 16 quoted lines
> When the index is unmerged, e.g.
> 
> 	$ git ls-files -u
>         100644 faf413748eb6ccb15161a212156c5e348302b1b6 1	setup.c
>         100644 145eca50f41d811c4c8fcb21ed2604e6b2971aba 2	setup.c
>         100644 cb9558c49b6027bf225ba2a6154c4d2a52bcdbe2 3	setup.c
> 
> running "git grep" for work tree files repeats hits for each unmerged
> stage.
> 
> 	$ git grep -n -e setup_work_tree -- '*.[ch]'
>         setup.c:209:void setup_work_tree(void)
>         setup.c:209:void setup_work_tree(void)
>         setup.c:209:void setup_work_tree(void)
> 
> This should fix it.

Does this change the behavior of grep --cached? IOW, listing the same hit more than once when --cached is given is a feature, IMHO.

-- Hannes
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 5 in “git grep shows the same hit repeatedly for unmerged paths”
  1. git grep shows the same hit repeatedly for unmerged pathsJunio C Hamano, Dec 6, 2007
  2. Johannes SixtDec 6, 2007
  3. Junio C HamanoDec 6, 2007
  4. Johannes SixtDec 6, 2007
  5. Junio C HamanoDec 6, 2007

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.