From: Patrick Steinhardt <ps@pks.im>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: Meet Soni <meetsoni3017@gmail.com>,
git@vger.kernel.org, christian.couder@gmail.com,
shejialuo@gmail.com,
Ghanshyam Thakkar <shyamthakkar001@gmail.com>
Subject: Re: [GSoC][Proposal RFC] Consolidate ref-related functionality into git-refs
Date: Fri, 4 Apr 2025 13:48:21 +0200 [thread overview]
Message-ID: <Z-_HBe1lOu6_oRbr@pks.im> (raw)
In-Reply-To: <CAOLa=ZQ4nTP7Ls=JsnQSbvpvw+OhjXqqoQxpsTKA0x-HxaDH5A@mail.gmail.com>
On Fri, Apr 04, 2025 at 04:46:58AM -0700, Karthik Nayak wrote:
> Meet Soni <meetsoni3017@gmail.com> writes:
>
> [snip]
>
> > Command mapping and naming:
> > ---------------------------
> >
> > I have taken reference for potential names for these subcommands from Patrick’s
> > suggestion (https://gitlab.com/gitlab-org/git/-/issues/330):
> >
> > # Replaces git-show-ref(1) and git-for-each-ref(1).
> > $ git refs list
> >
> > # Replaces `git show-ref --exists`.
> > $ git refs exist
> >
> > # Replaces `git show-ref --verify <ref>`.
> > $ git refs show
> >
> > # Replaces git-symbolic-ref(1) to show a ref.
> > $ git refs resolve
> >
> > # Replaces git-pack-ref(1).
> > $ git refs pack
> >
> > # Replaces git-update-ref(1).
> > $ git refs write
> >
> > # Replaces git-check-ref-format(1).
> > $ git refs check-format
> >
>
> One other command that I noticed, which we didn't talk about it 'git
> reflog'. I would think, it would be nice to also fit this as 'git refs
> logs', but it doesn't have to be part of GSoC.
Wouldn't that become awkward though as you now basically have
subsubcommands? `git refs log expire`, `git refs log exists` and
related.
Patrick
next prev parent reply other threads:[~2025-04-04 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 1:37 [GSoC][Proposal RFC] Consolidate ref-related functionality into git-refs Meet Soni
2025-04-02 8:21 ` Patrick Steinhardt
2025-04-03 10:05 ` Meet Soni
2025-04-03 10:28 ` Patrick Steinhardt
2025-04-04 11:46 ` Karthik Nayak
2025-04-04 11:48 ` Patrick Steinhardt [this message]
2025-04-04 11:52 ` Karthik Nayak
2025-04-04 12:24 ` [GSoC][Proposal RFC v2] " Meet Soni
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=Z-_HBe1lOu6_oRbr@pks.im \
--to=ps@pks.im \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=meetsoni3017@gmail.com \
--cc=shejialuo@gmail.com \
--cc=shyamthakkar001@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.