All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Pete Harlan <pchpublic88@gmail.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
	git@vger.kernel.org, Michael J Gruber <git@drmicha.warpmail.net>
Subject: Re: [PATCH 1/5] status: document the -v/--verbose option
Date: Thu, 23 Apr 2015 18:44:58 -0700	[thread overview]
Message-ID: <xmqq4mo62tb9.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAM=ud8zLDTYUp12BsVjWH5=8rg=HxbtdBxL2L9x=3+FQVJBqrQ@mail.gmail.com> (Pete Harlan's message of "Thu, 23 Apr 2015 17:27:47 -0700")

Pete Harlan <pchpublic88@gmail.com> writes:

> 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`?
>
> --Pete
>
> (Sorry for not replying to the email; bit of a mess here in my setup.)

Duh!

I see "git commit" documentation does not have these extra "like the
output of..." bits.  Perhaps we can do without it for the sake of
both brevity and risk avoidance?

Will push out with --cached bit swapped for tonight on 'pu'.

  reply	other threads:[~2015-04-24  1:45 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 [this message]
2015-04-24 16:46 ` Michael Haggerty
  -- 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=xmqq4mo62tb9.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.