From: Junio C Hamano <gitster@pobox.com>
To: "Mansi Singh via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Mansi Singh <mansimaanu8627@gmail.com>
Subject: Re: [PATCH] t1900: add tests for git repo structure subcommand
Date: Mon, 09 Mar 2026 20:35:28 -0700 [thread overview]
Message-ID: <xmqqsea8xsov.fsf@gitster.g> (raw)
In-Reply-To: <pull.2066.git.1773112159662.gitgitgadget@gmail.com> (Mansi Singh via GitGitGadget's message of "Tue, 10 Mar 2026 03:09:19 +0000")
"Mansi Singh via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Mansi Singh <mansimaanu8627@gmail.com>
>
> The t1900 test file covers git repo info thoroughly but has
> no tests for the git repo structure subcommand. Add basic
> tests to verify that:
>
> - git repo structure succeeds and produces no stderr output
> - git repo structure --format=keyvalue outputs expected keys
> - git repo structure --format=nul succeeds
> - git repo structure rejects an unknown format
Ask those who have worked on the relevant command to review by
adding them on the Cc: line.
next prev parent reply other threads:[~2026-03-10 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 3:09 [PATCH] t1900: add tests for git repo structure subcommand Mansi Singh via GitGitGadget
2026-03-10 3:35 ` Junio C Hamano [this message]
2026-03-10 13:34 ` K Jayatheerth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqsea8xsov.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=mansimaanu8627@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox