From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Erlend Aasland <Erlend-A@innova.no>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] branch: delete now accepts '-' as branch name
Date: Mon, 21 Feb 2022 09:13:53 -0800 [thread overview]
Message-ID: <xmqqwnhota5q.fsf@gitster.g> (raw)
In-Reply-To: <220221.86pmngb22e.gmgdl@evledraar.gmail.com> ("Ævar Arnfjörð Bjarmason"'s message of "Mon, 21 Feb 2022 17:34:01 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
>> Continuing the "thinking aloud" a bit, I _think_ this tells us these
>> things:
>>
>> * @{-1} has way too many letters to type to be liked by users, who
>> won't learn or remember what they do not appreciate (and do not
>> blame them---it is a bad notation).
>>
>> * @{-<n>} may have been a generalized way that satisfied geeky mind
>> while being implemented, but the users only need the "last one"
>> and no such generalization.
>>
>> If it is too late for a more easy-to-type-and-pleasant-to-eyes
>> notation, perhaps "@-", that does not have downsides of "-" or
>> "@{-1}", I have to wonder.
>
> I too find the syntax really annoying to type.
>
> I wonder if we couldn't say that:
> ...
We could, but I do not think I like any of it, except for adding
"@-". We learned that we do not need @{-4} generalization and
people only want "the last one" with nothing else. It is repeating
the same mistake without learning any from the lesson to take any
random string that follows @ as if it is inside @{}, I am afraid.
P.S. It seems it is holiday around here and I hear it is at GitHub,
too, so I expect the day to be slow and my presence may be sporadic.
next prev parent reply other threads:[~2022-02-21 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 14:08 [PATCH] branch: delete now accepts '-' as branch name Erlend Egeberg Aasland via GitGitGadget
2022-02-16 16:54 ` Junio C Hamano
2022-02-16 19:03 ` Eric Sunshine
2022-02-16 19:41 ` Junio C Hamano
2022-02-16 23:06 ` Erlend Aasland
2022-02-17 17:13 ` Eric Sunshine
2022-02-17 18:41 ` Junio C Hamano
2022-02-21 16:34 ` Ævar Arnfjörð Bjarmason
2022-02-21 17:13 ` Junio C Hamano [this message]
2022-02-21 19:20 ` Ævar Arnfjörð Bjarmason
2022-02-22 11:05 ` Erlend Aasland
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwnhota5q.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Erlend-A@innova.no \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).