From: git@jowil.de
To: git@vger.kernel.org
Subject: git tag -a HEAD leads to ambiguous branch name
Date: Wed, 27 Nov 2024 01:14:23 +0100 [thread overview]
Message-ID: <47cdf937-6192-4c83-a0e5-700e98f36c1e@jowil.de> (raw)
Good evening,
today I encountered a warning using git version 2.39.0.windows.2:
/warning: refname 'HEAD' is ambiguous./
It turned out, having written
/git tag -a HEAD -m "Some message."/
was the culprit.
As
/git branch HEAD/
yields the following error
/fatal: 'HEAD' is not a valid branch name/
I wanted to aks, whether a similar check should be applied to tag names.
Best regards
Johannes Wilde
next reply other threads:[~2024-11-27 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 0:14 git [this message]
2024-11-27 14:27 ` git tag -a HEAD leads to ambiguous branch name Jeff King
2024-11-27 23:30 ` Junio C Hamano
2024-12-01 22:44 ` Jeff King
2024-12-02 4:38 ` 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=47cdf937-6192-4c83-a0e5-700e98f36c1e@jowil.de \
--to=git@jowil.de \
--cc=git@vger.kernel.org \
/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).