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: Sat, 17 Oct 2026 09:59:50 -0700 [thread overview]
Message-ID: <xmqqbj8sb6ux.fsf@gitster.g> (raw)
In-Reply-To: <3d9463a2-d099-4f9d-a380-4c5036da1c20@app.fastmail.com> (Kristoffer Haugsbakk's message of "Sat, 17 Oct 2026 18:43:05 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> It replaces my want to use `@` which means that what you wrote
> back then:[1]
>
> JCH> I suspect that it is much more productive to deprecate and remove
> JCH> "@" that is a built-in synomym for HEAD (but "refs/remotes/origin/@"
> JCH> does not act as a synonym for "refs/remotes/origin/HEAD"). [...]
>
> Would not affect me. (Not that I believe that it would happen.)
I do not think it would happen, either. There are many things in
Git that I have publicly said are poorly designed, but that we
cannot correct due to heavy inertia.
next prev parent reply other threads:[~2026-10-17 16:59 UTC|newest]
Thread overview: 16+ 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
2026-10-17 16:43 ` Kristoffer Haugsbakk
2026-10-17 16:59 ` 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=xmqqbj8sb6ux.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 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.