From: Junio C Hamano <gitster@pobox•com>
To: Meet Soni <meetsoni3017@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: [GSoC][RFC PATCH 0/2] Add refs list subcommand
Date: Sat, 14 Jun 2025 16:45:31 -0700 [thread overview]
Message-ID: <xmqqsek16g6c.fsf@gitster.g> (raw)
In-Reply-To: <20250614070536.17320-1-meetsoni3017@gmail.com> (Meet Soni's message of "Sat, 14 Jun 2025 12:35:34 +0530")
Meet Soni <meetsoni3017@gmail•com> writes:
> This RFC is meant to start a broader discussion on:
>
> - The desired default behavior of pattern matching in git refs list
>
> - Which features from both git-show-ref and git-for-each-ref should be
> preserved, rethought, or dropped
>
> - How much backward compatibility we want to offer, and through what
> interface (e.g., compatibility flags)
>
> Feedback and thoughts on these topics would be very welcome.
In addition to these three points, 0th point perhaps is "Is it
desirable to unify these two commands in the first place?"
I only use "show-ref" when I care about a single ref in a script,
expecting to be able to switch on its exit status. Everything else
I'd use for-each-ref.
But then that particular unique advantage of show-ref over for-each-ref
can be done with "rev-parse --verify".
So, I'd rather not to see yet another command to do the same thing.
Rather, is it insufficient to just use for-each-ref or rev-parse,
let the sleeping show-ref alone, and be happy?
> Meet Soni (2):
> builtin/refs: add list subcommand
> t: add tests for refs list subcommand
>
> Documentation/git-refs.adoc | 25 ++++++++
> builtin/refs.c | 110 ++++++++++++++++++++++++++++++++++++
> t/meson.build | 1 +
> t/t1461-refs-list.sh | 95 +++++++++++++++++++++++++++++++
> 4 files changed, 231 insertions(+)
> create mode 100755 t/t1461-refs-list.sh
next prev parent reply other threads:[~2025-06-14 23:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 7:05 [GSoC][RFC PATCH 0/2] Add refs list subcommand Meet Soni
2025-06-14 7:05 ` [GSoC][RFC PATCH 1/2] builtin/refs: add " Meet Soni
2025-06-14 7:05 ` [GSoC][RFC PATCH 2/2] t: add tests for refs " Meet Soni
2025-06-14 23:45 ` Junio C Hamano [this message]
2025-06-17 11:51 ` [GSoC][RFC PATCH 0/2] Add " Meet Soni
-- strict thread matches above, loose matches on Subject: below --
2025-06-27 7:49 Meet Soni
2025-06-27 18:03 ` Junio C Hamano
2025-06-28 8:05 ` shejialuo
2025-06-30 14:05 ` Junio C Hamano
2025-07-06 12:58 ` shejialuo
2025-06-30 3:53 ` Meet Soni
2025-06-30 20:10 ` Junio C Hamano
2025-07-09 13:36 ` 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=xmqqsek16g6c.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=meetsoni3017@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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