All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Han-Wen Nienhuys <hanwenn@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Subject: [PATCH 3/9] refs/reftable: skip duplicate name checks
Date: Wed, 3 Apr 2024 13:21:32 +0200	[thread overview]
Message-ID: <Zg07vKzkeXt7l8RW@tanuki> (raw)
In-Reply-To: <CAOw_e7YspBkOo7QE0Z3QqWXd6P1OVnF9j3q7ircrce25KNbKLw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

On Wed, Apr 03, 2024 at 11:47:10AM +0200, Han-Wen Nienhuys wrote:
> I can't remember why I did not rely on the available routine (did it
> not exist at the time? or maybe I assumed the files backend relied on
> the file system to enforce well-formedness).  If the functionality is
> covered by refs_verify_refname_available, it's probably better to rip
> out of the reftable library (essentially, just delete refname.c and
> friends) rather than disable it. I am assuming libgit2 will have an
> equivalent routine as well.

Yeah, I was on the fence whether I do or don't want to delete the
corresponding code. In any case, without Git as a user it's much more
likely to start bitrotting even though we do have some unit tests in
this area. Whether libgit2 does have a similar generic D/F check I
cannot remember though -- it's been a very long time since I have
written the reftable backend for libgit2, and the pull request is
bitrotting.

My assumption is that as soon as there is going to be a second user of
this library we'll have to do some cleanups regardless. So I'm inclined
to delete the code now and potentially bring it back if we ever see that
it's indeed important for external users.

Patrick

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-03 11:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03  9:47 Subject: [PATCH 3/9] refs/reftable: skip duplicate name checks Han-Wen Nienhuys
2024-04-03 11:21 ` Patrick Steinhardt [this message]
2024-04-03 16:21   ` Junio C Hamano

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=Zg07vKzkeXt7l8RW@tanuki \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=hanwenn@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.