Re: What's cooking in git.git (Nov 2008, #06; Wed, 26)

From: Junio C Hamano <gitster@pobox.com>
Date: Dec 13, 2008, 05:51 UTC
Message-ID: <7vvdto7hcg.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <fcaeb9bf0812120854k1c366327o9bc696184ea4f02e@mail.gmail.com>

"Nguyen Thai Ngoc Duy" <pclouds@gmail.com> writes:

Show 9 quoted lines

> On 12/12/08, Johannes Sixt <j.sixt@viscovery.net> wrote:
> ...
>> But what if the same persion notices a #define in a kdeutils header file
>>  and want's to know whether it is unused in order to remove it:
>>
>>     $ git grep FOO
>>     kdeutils/foo.h:#define FOO bar
>
> "git grep --cached FOO" ?

That should behave identically when the work tree does not have change since the index, and by definition paths outside the checkout area in the "sparse" mode cannot have changes, so "git grep FOO" should behave the same and should find it.

$ 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.