From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: "Bence Csókás" <bence.csokas@arm.com>,
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>,
git@vger.kernel.org, "Jeff King" <peff@peff.net>
Subject: Re: [Bug] Porcelain allows creation of '@' branch
Date: Fri, 16 Oct 2026 11:40:18 -0700 [thread overview]
Message-ID: <xmqqld7xfq0d.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CA7vxpmhVB3pi3gpVcbtCS_yHtA+a1Ud25P00JDAqboAA@mail.gmail.com> (D. Ben Knoble's message of "Fri, 16 Oct 2026 14:09:57 -0400")
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
> But shorthands are convenient day-to-day. What's a bad habit about that?
A shorthand may be convenient, but not all "convenient" things are
automatically good. A poorly designed, ill-thought-out shorthand
that forbids a branch whose name follows a set of clearly defined
rules perfectly well is good example.
prev parent reply other threads:[~2026-10-16 18:40 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
2026-10-16 18:40 ` Junio C Hamano [this message]
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=xmqqld7xfq0d.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