All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Bence Csókás" <bence.csokas@arm.com>
Cc: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	 "D. Ben Knoble" <ben.knoble@gmail.com>,
	 git@vger.kernel.org,  Jeff King <peff@peff.net>
Subject: Re: [Bug] Porcelain allows creation of '@' branch
Date: Fri, 16 Oct 2026 08:35:12 -0700	[thread overview]
Message-ID: <xmqq4ielirpr.fsf@gitster.g> (raw)
In-Reply-To: <fc3de093-a051-415c-b40e-f9df5c914704@arm.com> ("Bence Csókás"'s message of "Thu, 15 Oct 2026 09:58:31 +0200")

Bence Csókás <bence.csokas@arm.com> writes:

> On 2026. 09. 03. 14:35, Bence Csókás wrote:
>> On 2026. 09. 03. 10:38, Kristoffer Haugsbakk wrote:
>>> Not a bug (2024) https://lore.kernel.org/git/xmqqy12z7eti.fsf@gitster.g/
>>>
>>>      I suspect that it is much more productive to deprecate and remove
>>>      "@" that is a built-in synomym for HEAD (but "refs/remotes/origin/@"
>>>      does not act as a synonym for "refs/remotes/origin/HEAD"). [...]
>> I would not want to see @ removed, I have abandoned using HEAD years
>> ago, too much typing (especially if you want to express more complex
>> things, e.g. `git range-diff long-branch-name{^..otherbranch,..@}`, to
>> pick an example out of my bash-history).
>>
>> Bence
>
> P.S.:
>
> $  history | grep 'git .*@' | wc -l
> 74
> $  history | grep HEAD | wc -l
> 0
>
> ;)

You have some unlearning of a bad habit to do, then ;-)

  reply	other threads:[~2026-10-16 15:35 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 [this message]
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

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=xmqq4ielirpr.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.