From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Philippe Vaucher <philippe.vaucher@gmail.com>,
git@vger.kernel.org, Rafael Magana <raf.magana@gmail.com>
Subject: Re: Suggestions to make git easier to understand
Date: Thu, 11 Aug 2011 15:39:13 -0700 [thread overview]
Message-ID: <7vmxffpo8e.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20110811221627.GA32005@elie.gateway.2wire.net> (Jonathan Nieder's message of "Thu, 11 Aug 2011 17:16:27 -0500")
Jonathan Nieder <jrnieder@gmail.com> writes:
>> Maybe
>> --cached could have an alias like --index-only for things to be more
>> intuitive as well.
>>
>> `git rm --index-only somefile` is more understandable than `git rm
>> --cached somefile` imho.
>>
>> Also, in ls-files, --stage could maybe use an alias like --contents
>> for it to be more self-explanatory.
>
> These suggestions also seem sane.
The --index-only synonym was throwed around in a handful of discussions in
the past. It probably would not hurt, I would say.
I do not think "ls-files --contents" makes things any better, though.
Until a new user encounters a conflicted state, it might look like that
the primary point of "ls-files -s" is to show the object names, but it
also is important that it shows the stage numbers.
next prev parent reply other threads:[~2011-08-11 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 7:48 Suggestions to make git easier to understand Philippe Vaucher
2011-08-11 22:16 ` Jonathan Nieder
2011-08-11 22:39 ` Junio C Hamano [this message]
2011-08-11 23:08 ` Jonathan Nieder
2011-08-12 22:26 ` Jeff King
2011-08-15 10:15 ` Philippe Vaucher
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=7vmxffpo8e.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=philippe.vaucher@gmail.com \
--cc=raf.magana@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.
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).