All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Carlo Arenas <carenas@gmail.com>
Cc: gitmailinglist.bentolor@xoxy.net, git@vger.kernel.org
Subject: Re: Should `@` be really a valid git tag name?
Date: Fri, 17 Sep 2021 13:53:52 -0700	[thread overview]
Message-ID: <xmqq4kaihqjj.fsf@gitster.g> (raw)
In-Reply-To: <CAPUEspjbiNtffXatzNUUFYyZKRjcqetOTVqQX+MgZf_AJq9hnA@mail.gmail.com> (Carlo Arenas's message of "Fri, 17 Sep 2021 11:20:14 -0700")

Carlo Arenas <carenas@gmail.com> writes:

> On Fri, Sep 17, 2021 at 7:12 AM <gitmailinglist.bentolor@xoxy.net> wrote:
>>
>> A SO commenter pointed out, that git-check-ref-format forbids @ and
>> maybe I should report this as a potential bug. Is it?
>
> a reference that is named "@" only is invalid, but refs/tags/@ is not.

;-)  

"git check-ref-format master ; echo $?" would show that any single
level name is "forbidden", so probably the SO commenter (whatever
that is) was confused---it is not about @ at all.

In any case, a tag whose name is @ may be another source of
confusion in the modern world, after we added @ as a synonym to
HEAD.  I do not know, for example, offhand which between the HEAD or
that tag "git show @" would choose.  It makes sense to avoid it.

  reply	other threads:[~2021-09-17 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 11:20 Should `@` be really a valid git tag name? gitmailinglist.bentolor
2021-09-17 18:20 ` Carlo Arenas
2021-09-17 20:53   ` Junio C Hamano [this message]
2021-09-17 21:47     ` Jeff King
2021-09-17 22:58       ` Carlo Marcelo Arenas Belón
2021-09-17 23:06         ` Junio C Hamano
2021-09-18  0:21           ` Carlo Arenas
2021-09-18  0:25             ` Junio C Hamano
2021-09-18  4:53               ` Carlo Marcelo Arenas Belón
2021-09-18 13:45     ` Chris Torek

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=xmqq4kaihqjj.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitmailinglist.bentolor@xoxy.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 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.