From: Konstantin Khomoutov <kostix@bswap.ru>
To: Sergey Organov <sorganov@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>, Ivan Tham <pickfire@riseup.net>,
git@vger.kernel.org,
"brian m . carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH] branch: add '-' to delete previous branch
Date: Thu, 30 Apr 2020 19:27:53 +0300 [thread overview]
Message-ID: <20200430162753.pg6kpm6jlubotjlk@carbon> (raw)
In-Reply-To: <87imhihwbw.fsf@osv.gnss.ru>
On Wed, Apr 29, 2020 at 11:26:59PM +0300, Sergey Organov wrote:
[...]
> >> > In my opinion, it is fairly clear that 'git branch -D -' means "delete
> >> > the last branch", and not "delete a list of branches from stdin.
> >>
> >> Honestly, I'd never guess it'd "delete the last branch". No way.
> >
> > I'm having trouble understanding why. This is how 'git checkout -'
> > behaves, so I have no idea why 'git branch' wouldn't work the same
> > way.
>
> Well, if I knew 'git checkout -' does this, then yes, it'd be obvious.
> The problem is that I didn't. Well, then, as I said in my original
> reaction, I'm probably too late on this.
>
> BTW, it was not that easy to find it in the "git help checkout" even
> when I was specifically looking for it.
I would speculate that `git checkout -` may have learned about "-"
simply from the `cd -` form of the standard Unix shell (also codified by
POSIX [1]) which behaved that way - change the current directory to the
previous one - since forever. ;-)
1. https://pubs.opengroup.org/onlinepubs/9699919799/utilities/cd.html
next prev parent reply other threads:[~2020-04-30 16:58 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
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 [this message]
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
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=20200430162753.pg6kpm6jlubotjlk@carbon \
--to=kostix@bswap.ru \
--cc=git@vger.kernel.org \
--cc=me@ttaylorr.com \
--cc=pickfire@riseup.net \
--cc=sandals@crustytoothpaste.net \
--cc=sorganov@gmail.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).