From: "Miles Bader" <miles@gnu.org>
To: "Wincent Colaiuta" <win@wincent.com>
Cc: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: A few usability question about git diff --cached
Date: Fri, 5 Oct 2007 19:41:37 +0900 [thread overview]
Message-ID: <fc339e4a0710050341v11a7f9f7j3cf24403d2231886@mail.gmail.com> (raw)
In-Reply-To: <0A7AA9C3-6D9E-4B14-822D-05232F0EAF99@wincent.com>
On 10/5/07, Wincent Colaiuta <win@wincent.com> wrote:
> > Personally all I want is a short-option alias for --cached!
> >
> > Hopefully something easily type-able (not uppercase)...
>
> Did you see the aliases I posted earlier in the thread? I can't think
> of anything shorter or semantically clearer than "staged" and
> "unstaged".
The words are ok, I guess, but aliases are not a replacement for short
options.... really all frequently used, non-dangerous, options should
have a short variant (and diff --cached meets both criteria handily)!
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2007-10-05 10:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 12:27 A few usability question about git diff --cached Paolo Ciarrocchi
2007-10-04 12:54 ` Wincent Colaiuta
2007-10-05 5:59 ` Miles Bader
2007-10-05 10:27 ` Wincent Colaiuta
2007-10-05 10:41 ` Miles Bader [this message]
2007-10-04 12:56 ` Miklos Vajna
2007-10-04 13:10 ` Paolo Ciarrocchi
2007-10-04 13:14 ` Junio C Hamano
2007-10-04 13:39 ` Paolo Ciarrocchi
2007-10-04 14:09 ` Wincent Colaiuta
2007-10-04 14:34 ` Johannes Schindelin
2007-10-04 14:40 ` Junio C Hamano
2007-10-04 14:47 ` David Kastrup
2007-10-04 14:44 ` Matthieu Moy
2007-10-04 15:51 ` J. Bruce Fields
2007-10-04 16:02 ` Matthieu Moy
2007-10-04 16:19 ` J. Bruce Fields
2007-10-05 6:40 ` Matthieu Moy
2007-10-05 5:22 ` David Tweed
2007-10-04 15:49 ` Wincent Colaiuta
2021-08-14 19:31 Court Rankin
2023-01-12 11:54 Mohammed Al-Mahmeed
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=fc339e4a0710050341v11a7f9f7j3cf24403d2231886@mail.gmail.com \
--to=miles@gnu.org \
--cc=git@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=win@wincent.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 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 NNTP newsgroup(s).