Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: "D. Ben Knoble" <ben.knoble@gmail.com>,
	"Bence Csókás" <bence.csokas@arm.com>,
	git@vger.kernel.org, "Jeff King" <peff@peff.net>
Subject: Re: [Bug] Porcelain allows creation of '@' branch
Date: Fri, 16 Oct 2026 11:52:48 -0700	[thread overview]
Message-ID: <xmqqh5ilfpfj.fsf@gitster.g> (raw)
In-Reply-To: <d7450b0c-89ad-4963-9229-198f40cf72c1@app.fastmail.com> (Kristoffer Haugsbakk's message of "Fri, 16 Oct 2026 20:21:40 +0200")

"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

>> (Besides, the OP's grep also counts uses of
>> @{upstream}/@{u}/@{push}/reflog syntax/etc.)
>
> I set up `git symbolic-ref refs/H HEAD` after my first `@`
> conversation.[1]

That is funny and clever, but unfortunately it does not help solving
the problem that the @-shorthand "conveniently" squats there to make
your use of a branch named "@" hard or impossible.

  reply	other threads:[~2026-10-16 18:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 14:22 [Bug] Porcelain allows creation of '@' branch Bence Csókás
2026-08-31 19:59 ` D. Ben Knoble
2026-09-02  7:37   ` Jeff King
2026-09-03  8:38   ` Kristoffer Haugsbakk
2026-09-03 12:35     ` Bence Csókás
2026-09-03 15:14       ` Ben Knoble
2026-09-03 18:45         ` Junio C Hamano
2026-09-06  7:56           ` Kristoffer Haugsbakk
2026-10-15  7:58       ` Bence Csókás
2026-10-16 15:35         ` Junio C Hamano
2026-10-16 18:09           ` D. Ben Knoble
2026-10-16 18:21             ` Kristoffer Haugsbakk
2026-10-16 18:52               ` Junio C Hamano [this message]
2026-10-16 18:40             ` 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=xmqqh5ilfpfj.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=bence.csokas@arm.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    --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