public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, jltobler@gmail.com,
	avila.jn@gmail.com
Subject: Re: [PATCH v4 2/2] repo: add new flag --keys to git-repo-info
Date: Tue, 20 Jan 2026 07:05:45 +0100	[thread overview]
Message-ID: <aW8bOfVLcG58t-Uk@pks.im> (raw)
In-Reply-To: <20260119210932.68893-3-lucasseikioshiro@gmail.com>

On Mon, Jan 19, 2026 at 05:20:20PM -0300, Lucas Seiki Oshiro wrote:
> diff --git a/builtin/repo.c b/builtin/repo.c
> index 306d3fa2df..2f698c5253 100644
> --- a/builtin/repo.c
> +++ b/builtin/repo.c
> @@ -29,6 +30,7 @@ enum output_format {
>  	FORMAT_TABLE,
>  	FORMAT_KEYVALUE,
>  	FORMAT_NUL_TERMINATED,
> +	FORMAT_LINES
>  };
>  
>  struct field {

Tiny nit: we also tend to terminate the last enum value with a comma.
The reason here is that it makes it easier to add new values going
forward while only having to change one line.

> @@ -149,6 +151,32 @@ static int print_all_fields(struct repository *repo,
>  	return 0;
>  }
>  
> +static int print_keys(enum output_format format)
> +{
> +	char sep;
> +
> +	if (format == FORMAT_DEFAULT)
> +		format = FORMAT_LINES;
> +
> +	switch (format) {
> +	case FORMAT_LINES:
> +		sep = '\n';
> +		break;
> +	case FORMAT_NUL_TERMINATED:
> +		sep = '\0';
> +		break;
> +	default:
> +		die(_("--keys can only be used with --format=default or --format=nul"));

This error message isn't true anymore, as we also support
"--format=lines" now.

> @@ -162,6 +190,8 @@ static int parse_format_cb(const struct option *opt,
>  		*format = FORMAT_KEYVALUE;
>  	else if (!strcmp(arg, "table"))
>  		*format = FORMAT_TABLE;
> +	else if (!strcmp(arg, "lines"))
> +		*format = FORMAT_LINES;
>  	else if (!strcmp(arg, "default"))
>  		*format = FORMAT_DEFAULT;
>  	else

You also have to adapt `cmd_repo_structure()` to handle this new vaule.
Otherwise it would `BUG()`. I guess the most reasonable change here
would be to treat "lines" and "keyvalue" as equivalent?

Thanks!

Patrick

  reply	other threads:[~2026-01-20  6:05 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-07 19:02 [PATCH] repo: add new flag --keys to git-repo-info Lucas Seiki Oshiro
2025-12-07 22:14 ` Junio C Hamano
2025-12-08 16:33   ` Lucas Seiki Oshiro
2025-12-08  7:13 ` Patrick Steinhardt
2025-12-09 19:36 ` [PATCH v2 0/2] " Lucas Seiki Oshiro
2025-12-09 19:36   ` [PATCH v2 1/2] repo: add a default output format to enum output_format Lucas Seiki Oshiro
2026-01-05 14:18     ` Patrick Steinhardt
2026-01-07 21:28       ` Lucas Seiki Oshiro
2026-01-08  6:13         ` Patrick Steinhardt
2025-12-09 19:36   ` [PATCH v2 2/2] repo: add new flag --keys to git-repo-info Lucas Seiki Oshiro
2026-01-05 14:18     ` Patrick Steinhardt
2026-01-05 13:57   ` [PATCH v2 0/2] " Lucas Seiki Oshiro
2026-01-05 14:19     ` Patrick Steinhardt
2026-01-09 20:31 ` [PATCH v3 0/2] repo: add --format=default and --keys Lucas Seiki Oshiro
2026-01-10  6:48   ` Junio C Hamano
2026-01-10  7:02     ` Junio C Hamano
2026-01-09 20:31 ` [PATCH v3 1/2] repo: add a default output format to enum output_format Lucas Seiki Oshiro
2026-01-09 20:31 ` [PATCH v3 2/2] repo: add new flag --keys to git-repo-info Lucas Seiki Oshiro
2026-01-10 12:04   ` Jean-Noël AVILA
2026-01-10 22:00     ` Lucas Seiki Oshiro
2026-01-12  8:40   ` Patrick Steinhardt
2026-01-19 20:20 ` [PATCH v4 0/2] repo: add --format=default and --keys Lucas Seiki Oshiro
2026-01-19 20:20   ` [PATCH v4 1/2] repo: add a default output format to enum output_format Lucas Seiki Oshiro
2026-01-19 20:20   ` [PATCH v4 2/2] repo: add new flag --keys to git-repo-info Lucas Seiki Oshiro
2026-01-20  6:05     ` Patrick Steinhardt [this message]
2026-01-20 23:11       ` Lucas Seiki Oshiro
2026-01-21  7:19         ` Patrick Steinhardt
2026-01-21 14:38           ` Lucas Seiki Oshiro
2026-01-20  0:52   ` [PATCH v4 0/2] repo: add --format=default and --keys Junio C Hamano
2026-01-23 16:34 ` [PATCH v5 0/2] repo: add --keys and rename "keyvalue" to "lines" Lucas Seiki Oshiro
2026-01-23 16:34   ` [PATCH v5 1/2] repo: " Lucas Seiki Oshiro
2026-01-27  6:58     ` Patrick Steinhardt
2026-01-23 16:34   ` [PATCH v5 2/2] repo: add new flag --keys to git-repo-info Lucas Seiki Oshiro
2026-01-27  6:58     ` Patrick Steinhardt
2026-01-27 22:27       ` Lucas Seiki Oshiro
2026-02-14  0:35 ` [PATCH v6 0/2] repo: add --keys and rename "keyvalue" to "lines" Lucas Seiki Oshiro
2026-02-14  0:35   ` [PATCH v6 1/2] repo: rename the output format " Lucas Seiki Oshiro
2026-02-14  0:35   ` [PATCH v6 2/2] repo: add new flag --keys to git-repo-info Lucas Seiki Oshiro
2026-02-14 18:14   ` [PATCH v6 0/2] repo: add --keys and rename "keyvalue" to "lines" Junio C Hamano
2026-02-16  6:59     ` Patrick Steinhardt

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=aW8bOfVLcG58t-Uk@pks.im \
    --to=ps@pks.im \
    --cc=avila.jn@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jltobler@gmail.com \
    --cc=lucasseikioshiro@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