From: Eric Sunshine <sunshine@sunshineco.com>
To: Erlend Aasland <Erlend-A@innova.no>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] branch: delete now accepts '-' as branch name
Date: Thu, 17 Feb 2022 12:13:10 -0500 [thread overview]
Message-ID: <CAPig+cR0Ks2bnTRqs3uF4M+3q+n9X6pApBQ9HQTUq=zK5TpuXQ@mail.gmail.com> (raw)
In-Reply-To: <400A4D37-74EA-4F3B-BA3B-99FFDAE3CB3C@innova.no>
On Thu, Feb 17, 2022 at 7:51 AM Erlend Aasland <Erlend-A@innova.no> wrote:
> > On 16 Feb 2022, at 20:03, Eric Sunshine <sunshine@sunshineco.com> wrote:
> > Patches implementing this behavior for `git branch -D` have been submitted previously but were rejected (if I recall correctly) since "delete" is a destructive operation, unlike other cases in which `-` is accepted. A relatively recent submission and ensuing discussion is at [1].
> >
> > [1]: https://lore.kernel.org/git/20200501222227.GE41612@syl.local/T/
>
> Thanks for the heads-up regarding previous discussions, Eric.
>
> Until now, I've just been using the @{-1} notation, but - is very much faster
> to type ;)
>
> There are no new arguments pro this feature, so I guess the conclusion from
> 2020 still stands :)
Perhaps. Perhaps not. I may be misreading Junio's responses in this
thread, but it didn't seem like he was necessarily opposed to the
change. A documentation update as in [1] would be a good idea, though,
if resubmitted.
next prev parent reply other threads:[~2022-02-17 17:13 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 [this message]
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
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='CAPig+cR0Ks2bnTRqs3uF4M+3q+n9X6pApBQ9HQTUq=zK5TpuXQ@mail.gmail.com' \
--to=sunshine@sunshineco.com \
--cc=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.
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.