git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Miklos Vajna <vmiklos@frugalware.org>,
	Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: A few usability question about git diff --cached
Date: Thu, 04 Oct 2007 07:40:26 -0700	[thread overview]
Message-ID: <7vhcl79c4l.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710041534000.4174@racer.site> (Johannes Schindelin's message of "Thu, 4 Oct 2007 15:34:45 +0100 (BST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Thu, 4 Oct 2007, Junio C Hamano wrote:
>
>>  * --cached means work only on index and ignore work tree.
>
> I guess I could live with "--staged" as a synonym for "--cached" (and 
> maybe deprecating "--cached").

A handy mnemonic might be:

 * --index means work work tree through the index.  Once you get
   git, this is natural as you would not interact with files in
   the work tree that is not known to the index.

 * --cached means work only on the cached information in index.

Any change like swapping them or renaming --cached to --index
and making something else to mean what --index always meant will
break existing setups and people's scripts.  Won't happen.

Giving them synonyms without deprecation is a viable option, if
necessary.  I do not however see the need yet.  A few people who
haven't learned the lingo of the land yet can worry about
possible confusion, but I do not think that "worry" itself does
not count as real need.

  reply	other threads:[~2007-10-04 14:40 UTC|newest]

Thread overview: 24+ 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
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2021-08-14 19:31 Court Rankin
2023-01-12 11:54 Mohammed Al-Mahmeed
2024-07-02 14:13 Kenneth Porter
2024-07-02 14:13 Kenneth Porter

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=7vhcl79c4l.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=paolo.ciarrocchi@gmail.com \
    --cc=vmiklos@frugalware.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 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).