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

git-grep in sparse checkout

From
Matheus Tavares Bernardino <matheus.bernardino@usp.br>
Date
Oct 1, 2019, 13:06 UTC
Message-ID
<CAHd-oW7e5qCuxZLBeVDq+Th3E+E4+P8=WzJfK8WcG2yz=n_nag@mail.gmail.com>
Hi,

During Git Summit it was mentioned that git-grep searches outside sparsity pattern which is not aligned with user expectation. I took a quick look at it and it seems the reason is builtin/grep.c:grep_cache() (which also greps worktree) will grep the object store when a given index entry has the CE_SKIP_WORKTREE bit turned on.

From what I understand, this bit is used exactly for sparse checkouts (as described in Documentation/technical/index-format.txt[1]). But should we perhaps ignore it in git-grep to have the expected behavior? I'll be happy to send the patch if so, but I wanted to check with you first.

Grepping with --cached or in given trees objects would still grep outside the cone, but that is what one would expect, right? Or should we filter out what is outside of the cone for cached grep as well?

Thanks, Matheus

[1]: https://github.com/git/git/blob/master/Documentation/technical/index-format.txt#L101
Next: Bert Wesarg
Message 1 of 9 in “git-grep in sparse checkout”
  1. Matheus Tavares BernardinoOct 1, 2019
  2. Bert WesargOct 1, 2019
  3. Elijah NewrenOct 1, 2019
  4. Junio C HamanoOct 2, 2019
  5. Elijah NewrenOct 2, 2019
  6. Derrick StoleeOct 1, 2019
  7. Matheus Tavares BernardinoOct 2, 2019
  8. Junio C HamanoOct 2, 2019
  9. Derrick StoleeOct 2, 2019

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.