Re: [Bug] Porcelain allows creation of '@' branch
- From
- Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
- Date
- Sep 6, 2026, 07:56 UTC
- Message-ID
- <2e2dcf60-4175-4cc4-8379-f6618340da40@app.fastmail.com>
- In-Reply-To
- <xmqqmrtyb2dd.fsf@gitster.g>
On Thu, Sep 3, 2026, at 20:45, Junio C Hamano wrote:
Show 20 quoted lines
> Ben Knoble <ben.knoble@gmail.com> writes:
>
>>> Le 3 sept. 2026 à 08:36, Bence Csókás <bence.csokas@arm.com> a écrit :
>>>
>>> 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).
>>
>> Ditto, though thanks for digging up the reference. It will surely be important to justify when proposing to tighten the branch-mode rules.
>
> It is very unfortunate that the quote is partial and incomplete,
> though, and would not be a good input for people to decide on their
> own.Sorry that I misrepresented your post. The gist to me was that you weren’t interested in more code to deal with the `@` shorthand.