Git development
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] update-ref: add --rename option
Date: Mon, 15 Jun 2026 10:57:48 +0200	[thread overview]
Message-ID: <ai--jEk23E7RJPnc@pks.im> (raw)
In-Reply-To: <xmqqqzmbhikj.fsf@gitster.g>

On Fri, Jun 12, 2026 at 08:41:48AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> 
> > A slight tangent: this is part of why I really don't like commands that
> > determine their mode via flags: you now have to worry about every
> > combination of flags and whether they even make sense. With subcommands
> > we at least only have to worry about the set of flags that directly
> > apply to that given subcommand.
> >
> > Makes me wonder whether I should have a look at extending git-refs(1)
> > further:
> >
> >     git refs delete <ref> [<oldvalue>]
> >     git refs update <ref> <newvalue> [<oldvalue>]
> >     git refs rename <ref> <oldname> <newname>
> >
> > I always wanted to do this eventually so that we have one top-level
> > command that knows how to do "everything refs".
> 
> That may indeed be a better direction to go, but isn't update-ref
> the "everything refs" command already?

Well, it doesn't handle reading references, which is something that
git-refs(1) already knows to do.

Patrick

      reply	other threads:[~2026-06-15  8:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 21:35 [PATCH] update-ref: add --rename option Junio C Hamano
2026-06-10 21:28 ` [PATCH v2] " Junio C Hamano
2026-06-11 13:05   ` Patrick Steinhardt
2026-06-11 18:47     ` Junio C Hamano
2026-06-12  6:04       ` Patrick Steinhardt
2026-06-12 16:31       ` Junio C Hamano
2026-06-11 21:37 ` [PATCH v3] " Junio C Hamano
2026-06-12  6:00   ` Patrick Steinhardt
2026-06-12 15:41     ` Junio C Hamano
2026-06-15  8:57       ` Patrick Steinhardt [this message]

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=ai--jEk23E7RJPnc@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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