From: Jeff King <peff@peff.net>
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: Fri, 12 Aug 2011 16:26:27 -0600 [thread overview]
Message-ID: <20110812222626.GA7079@sigill.intra.peff.net> (raw)
In-Reply-To: <20110811221627.GA32005@elie.gateway.2wire.net>
On Thu, Aug 11, 2011 at 05:16:27PM -0500, Jonathan Nieder wrote:
> > http://raflabs.com/blogs/silence-is-foo/2011/04/07/staging-area-index-cache-git/
> >
> > I thought it made some good points about git being kinda confusing,
> > for example sentences like "Changed but not updated" in git status
> > could use a better sentence like "Changed but not in the index".
>
> Sounds reasonable (well, with some more precise wording to reflect
> that this means "changed but not all changes are reflected in the
> index").
Didn't we fix this already in 8009d83 (Better "Changed but not updated"
message in git-status, 2010-11-02)? Since v1.7.4, "git status" has
"Changes not staged for commit".
-Peff
next prev parent reply other threads:[~2011-08-12 22:26 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
2011-08-11 23:08 ` Jonathan Nieder
2011-08-12 22:26 ` Jeff King [this message]
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=20110812222626.GA7079@sigill.intra.peff.net \
--to=peff@peff.net \
--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).