From: Erlend Aasland <Erlend-A@innova.no>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] branch: delete now accepts '-' as branch name
Date: Tue, 22 Feb 2022 11:05:23 +0000 [thread overview]
Message-ID: <EA5CFD34-9BFF-4030-9188-37953D947437@innova.no> (raw)
In-Reply-To: <220221.86zgmk9g68.gmgdl@evledraar.gmail.com>
> On 21 Feb 2022, at 20:20, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>
> On Mon, Feb 21 2022, Junio C Hamano wrote:
>
>> Æ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).
+1
>>>> * @{-<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.
That harmonises with my usage.
> FWIW I often use @{-2}, @{-3} or equivalent, but never @{-28} or
> whatever.
Ditto; I mostly (at least 95% of the time) only use @{-1}. I've used other
small indices sporadically, but never a two-digit index.
> I think we should be careful to squat on namespaces needlessly, but if
> we can't think of a reason for why we wouldn't make typing some of these
> shortcuts easier...
IMO, it's not a shortcut if it's a hassle to type ;)
IIRC, the GitHub "Git Highlights" Blog has promoted the '-' trick every now and then.
> I haven't hacked it up (and won't any time soon), Erlend: are you interested? :)
There's a lot of suggestions floating around now, but sure, I'd be happy to give one of
them a go; at least as a proof-of-concept :)
Erlend
prev parent reply other threads:[~2022-02-22 11:05 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
2022-02-21 19:20 ` Ævar Arnfjörð Bjarmason
2022-02-22 11:05 ` Erlend Aasland [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
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=EA5CFD34-9BFF-4030-9188-37953D947437@innova.no \
--to=erlend-a@innova.no \
--cc=git@vger.kernel.org \
/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).