Re: [PATCH v2 1/2] repo: add a default output format to enum output_format

From: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Date: Jan 7, 2026, 21:28 UTC
Message-ID: <6D2CDFA6-FB52-4BFD-B800-B01B5E484038@gmail.com>
In-Reply-To: <aVvIQYdsrB8vAJ_R@pks.im>

> This is missing a test.

Indeed, I'll add a test for `--format=default`.

> It would for example be nice to verify that
> "--format=nul --format=default" does the expected thing.

Would it be necessary? We already have a test asserting that the last "--format" wins:

test_expect_success 'git repo info uses the last requested format' '
	echo "layout.bare=false" >expected &&
	git repo info --format=nul -z --format=keyvalue layout.bare >actual &&
	test_cmp expected actual
'

> Also, I didn't see `git repo structure` being updated. Should we do that
> so that both subcommands know to handle the "default" format?

Sure! I'll do that!

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