From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: git@jowil.de, Jeff King <peff@peff.net>
Subject: [PATCH 0/4] forbid HEAD as a tagname
Date: Mon, 2 Dec 2024 16:07:10 +0900 [thread overview]
Message-ID: <20241202070714.3028549-1-gitster@pobox.com> (raw)
So, here is a cleaned up version, which ended up to be a 4-patch
series.
- The first two steps move code around to get rid of the "strbuf_"
prefix from three misnamed helper functions that are more about
refs than they are about string manipulation operations. We now
have:
- copy_branchname() that copies a branchname while applying
interpret_branch_name() like @{-1} for previous branch, @{u}
for upstream, etc.
- check_branch_ref() and check_tag_ref() that are allowed to be a
bit stricter than check_refname_format(), e.g., to reject "HEAD"
as the name of a branch or a tag.
- The third step updates a test that assumes HEAD can be usable as
the name of a tag, but the breakage the test tries to protect is
not specific to any tagname.
- The final step then forbids "git tag" from using "HEAD" as the
name of a tag.
Junio C Hamano (4):
refs: move ref name helpers around
refs: drop strbuf_ prefix from helpers
t5604: do not expect that HEAD is a valid tagname
tag: "git tag" refuses to use HEAD as a tagname
branch.c | 2 +-
builtin/branch.c | 10 ++++----
builtin/check-ref-format.c | 2 +-
builtin/checkout.c | 2 +-
builtin/merge.c | 2 +-
builtin/tag.c | 13 +----------
builtin/worktree.c | 8 +++----
gitweb/gitweb.perl | 2 +-
object-name.c | 36 -----------------------------
refs.c | 47 ++++++++++++++++++++++++++++++++++++++
refs.h | 29 +++++++++++++++++++++++
strbuf.h | 22 ------------------
t/t5604-clone-reference.sh | 6 ++---
t/t7004-tag.sh | 6 +++++
14 files changed, 100 insertions(+), 87 deletions(-)
--
2.47.1-514-g9b43e7ecc4
next reply other threads:[~2024-12-02 7:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 7:07 Junio C Hamano [this message]
2024-12-02 7:07 ` [PATCH 1/4] refs: move ref name helpers around Junio C Hamano
2024-12-02 20:37 ` Jeff King
2024-12-03 1:23 ` Junio C Hamano
2024-12-02 7:07 ` [PATCH 2/4] refs: drop strbuf_ prefix from helpers Junio C Hamano
2024-12-02 20:51 ` Jeff King
2024-12-02 7:07 ` [PATCH 3/4] t5604: do not expect that HEAD is a valid tagname Junio C Hamano
2024-12-02 12:19 ` Kristoffer Haugsbakk
2024-12-02 21:00 ` Jeff King
2024-12-02 21:09 ` Kristoffer Haugsbakk
2024-12-03 1:29 ` Junio C Hamano
2024-12-05 20:25 ` Jeff King
2024-12-02 20:52 ` Jeff King
2024-12-02 7:07 ` [PATCH 4/4] tag: "git tag" refuses to use HEAD as a tagname Junio C Hamano
2024-12-02 10:54 ` Patrick Steinhardt
2024-12-02 13:01 ` shejialuo
2024-12-03 1:30 ` Junio C Hamano
2024-12-05 20:26 ` Jeff King
2024-12-05 20:27 ` Jeff King
2024-12-02 20:42 ` Rubén Justo
2024-12-03 1:35 ` Junio C Hamano
2024-12-02 21:03 ` Jeff King
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=20241202070714.3028549-1-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@jowil.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 NNTP newsgroup(s).