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

git grep --no-index and absolute paths don't work?

From
Bert Wesarg <bert.wesarg@googlemail.com>
Date
Oct 21, 2011, 06:34 UTC
Message-ID
<CAKPyHN138OZRt_3PT5ChuTpSEuOdybnyAj8Baqr=3OD=y==jgw@mail.gmail.com>
Hi,
I'm currently  totally confused, that a
    git grep --no-index foo /usr/include

does not work. I know that the documentation says "in the current directory" for the --no-index flag. But this does not work ether:

    cd ~; git grep --no-index foo ~/.bashrc

They all fail with 'is outside repository'. Which is for itself vary misleading, because I intentionally said --no-index.

Any input is appreciate.
Thanks.
Bert
Next: Carlos Martín Nieto
Message 1 of 6 in “git grep --no-index and absolute paths don't work?”
  1. Bert WesargOct 21, 2011
  2. Carlos Martín NietoOct 21, 2011
  3. Lars NoschinskiOct 21, 2011
  4. Bert WesargOct 21, 2011
  5. Junio C HamanoOct 21, 2011
  6. Bert WesargOct 21, 2011

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.