From: Han-Wen Nienhuys <hanwenn@gmail.com>
To: git <git@vger.kernel.org>, Patrick Steinhardt <ps@pks.im>
Subject: Subject: [PATCH 3/9] refs/reftable: skip duplicate name checks
Date: Wed, 3 Apr 2024 11:47:10 +0200 [thread overview]
Message-ID: <CAOw_e7YspBkOo7QE0Z3QqWXd6P1OVnF9j3q7ircrce25KNbKLw@mail.gmail.com> (raw)
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.
--
Han-Wen Nienhuys - hanwenn@gmail.com - http://www.xs4all.nl/~hanwen
next reply other threads:[~2024-04-03 9:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 9:47 Han-Wen Nienhuys [this message]
2024-04-03 11:21 ` Subject: [PATCH 3/9] refs/reftable: skip duplicate name checks Patrick Steinhardt
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=CAOw_e7YspBkOo7QE0Z3QqWXd6P1OVnF9j3q7ircrce25KNbKLw@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).