Re: [RFC PATCH 3/7] t3705: add tests for `git add` in sparse checkouts

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 18, 2021, 19:05 UTC
Message-ID: <xmqq5z2pgprt.fsf@gitster.g>
In-Reply-To: <20210218143837.16527-1-matheus.bernardino@usp.br>

Matheus Tavares <matheus.bernardino@usp.br> writes:

Show 10 quoted lines

> Then, the test would become:
>
> 	setup_sparse_entry &&
> 	test-tool cached_mtime sparse_entry >before &&
> 	test-tool chmtime -60 sparse_entry &&
> 	git add --refresh sparse_entry &&
> 	test-tool cached_mtime sparse_entry >after &&
> 	test_cmp before after
>
> What do you think?

I do not see much point in introducing a duplicated "ls-files --debug" that gives only a subset of its output. Even if we add test-tool, we would need to reserve the right to change its output format any time, so I am not sure what we'd be gaining by avoiding the use of existing one.

Thanks.

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