From: Taylor Hedberg <tmhedberg@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: [RFC] Delete current branch
Date: Fri, 19 Jul 2013 13:08:30 -0400 [thread overview]
Message-ID: <20130719170830.GD5999@euporie> (raw)
In-Reply-To: <7vppuewl6h.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Junio C Hamano, Fri 2013-07-19 @ 09:48:06-0700:
> But there is a very commonly accepted long tradition for "-" to mean
> "read from the standard input", so we cannot reuse it to mean "the
> branch I was previously on" for every command without first making
> sure the command will never want to use "-" for the other common
> purpose.
It may be worth noting that Bash (and probably other shells as well)
allow you to type `cd -` to switch back to the previous working
directory. I always (apparently mistakenly) assumed that
`git checkout -` was deliberately designed to mirror that shortcut. I
think the symmetry gives it some credibility, in any case. This
alternative meaning for - is not totally without precedent.
What would it mean to check out the standard input, anyway? I cannot see
how that could ever make sense, unless `git checkout` gains some
additional capaabilities that are unrelated to its current purpose.
Maybe I am just being myopic, though.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-19 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 10:35 [RFC] Delete current branch Ramkumar Ramachandra
2013-07-19 14:28 ` Andreas Schwab
2013-07-19 14:35 ` Ramkumar Ramachandra
2013-07-19 15:08 ` Junio C Hamano
2013-07-19 15:42 ` Ramkumar Ramachandra
2013-07-19 16:48 ` Junio C Hamano
2013-07-19 16:50 ` Ramkumar Ramachandra
2013-07-19 17:08 ` Taylor Hedberg [this message]
2013-07-19 19:15 ` Junio C Hamano
2013-07-19 22:52 ` 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=20130719170830.GD5999@euporie \
--to=tmhedberg@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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.