From: Michael Haggerty <mhagger@alum.mit.edu>
To: Pete Harlan <pchpublic88@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: [PATCH 1/5] status: document the -v/--verbose option
Date: Fri, 24 Apr 2015 18:46:49 +0200 [thread overview]
Message-ID: <553A7379.6030408@alum.mit.edu> (raw)
In-Reply-To: <CAM=ud8zLDTYUp12BsVjWH5=8rg=HxbtdBxL2L9x=3+FQVJBqrQ@mail.gmail.com>
On 04/24/2015 02:27 AM, Pete Harlan wrote:
> Junio writes:
>> Michael Haggerty <mhagger@alum.mit.edu> writes:
>>
>>> Document `git status -v`, including its new doubled `-vv` form.
>>>
>>> Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
>>> ---
>>
>> Will queue on mg/status-v-v series, which did add description for
>> "commit -v", but "status -v" did not have the description to begin
>> with and we missed it.
> [...]
>>> +-v::
>>> +--verbose::
>>> + In addition to the names of files that have been changed, also
>>> + show the textual changes that are staged to be committed
>>> + (i.e., like the output of `git diff`). If `-v` is specified
>
> Should this be `git diff --cached`?
>
>>> + twice, then also show the changes in the working tree that
>>> + have not yet been staged (i.e., like the output of `git diff
>>> + --cached`).
>
> ...and should this just be `git diff`?
Yes, you're right. Thanks for catching this, Pete. The shorter the
patch, the higher the error density :-(
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
next prev parent reply other threads:[~2015-04-24 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 0:27 [PATCH 1/5] status: document the -v/--verbose option Pete Harlan
2015-04-24 1:44 ` Junio C Hamano
2015-04-24 16:46 ` Michael Haggerty [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-23 12:27 [PATCH 0/5] Tweak the 2.4.0 release notes and related docs Michael Haggerty
2015-04-23 12:27 ` [PATCH 1/5] status: document the -v/--verbose option Michael Haggerty
2015-04-23 18:26 ` 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=553A7379.6030408@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pchpublic88@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).