From: Sergey Organov <sorganov@gmail.com>
To: Ivan Tham <pickfire@riseup.net>
Cc: git@vger.kernel.org, "brian m . carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] branch: add '-' to delete previous branch
Date: Wed, 29 Apr 2020 16:37:27 +0300 [thread overview]
Message-ID: <877dxyo1k8.fsf@osv.gnss.ru> (raw)
In-Reply-To: <20200429130133.520981-1-pickfire@riseup.net> (Ivan Tham's message of "Wed, 29 Apr 2020 21:01:33 +0800")
Ivan Tham <pickfire@riseup.net> writes:
> Add support to delete previous branch from git checkout/switch to have
> feature parity with git switch -.
Maybe I'm late on this, but to me, who leaves in the Linux world,
"a_command -" strongly suggests a_command will read further input
from stdin.
[...]
> +To delete the previous branch::
> ++
> +------------
> +$ git branch -D -
... so this suggests that the command, when used like this:
$ echo "branch_name" | git branch -D -
will delete "branch_name" rather than some "previous" branch, whatever
that means.
Is this short-cut /that/ important to create yet another confusion?
-- Sergey
next prev parent reply other threads:[~2020-04-29 13:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 13:01 [PATCH] branch: add '-' to delete previous branch Ivan Tham
2020-04-29 13:37 ` Sergey Organov [this message]
2020-04-29 19:00 ` Taylor Blau
2020-04-29 19:06 ` Eric Sunshine
2020-04-29 19:50 ` Sergey Organov
2020-04-29 19:57 ` Taylor Blau
2020-04-29 20:22 ` Junio C Hamano
2020-04-29 20:35 ` Taylor Blau
2020-04-29 20:39 ` Junio C Hamano
2020-04-29 20:37 ` Junio C Hamano
2020-04-29 20:26 ` Sergey Organov
2020-04-30 16:27 ` Konstantin Khomoutov
2020-04-30 19:52 ` Junio C Hamano
2020-05-01 9:18 ` Sergey Organov
2020-05-01 9:44 ` Konstantin Khomoutov
2020-05-01 10:22 ` Sergey Organov
2020-05-01 22:22 ` Taylor Blau
2020-04-30 3:43 ` Ivan Tham
2020-04-29 19:27 ` Junio C Hamano
2020-04-29 19:31 ` Randall S. Becker
2020-04-29 19:55 ` Sergey Organov
2020-04-29 18:58 ` Taylor Blau
2020-04-30 14:52 ` Ivan Tham
2020-04-30 15:59 ` Taylor Blau
2020-04-30 19:51 ` 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=877dxyo1k8.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=git@vger.kernel.org \
--cc=pickfire@riseup.net \
--cc=sandals@crustytoothpaste.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.