From: Junio C Hamano <gitster@pobox•com>
To: Michael Haggerty <mhagger@alum•mit.edu>
Cc: 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 11:26:31 -0700 [thread overview]
Message-ID: <xmqqvbgm3dm0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1429792070-22991-2-git-send-email-mhagger@alum.mit.edu> (Michael Haggerty's message of "Thu, 23 Apr 2015 14:27:46 +0200")
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.
Thanks.
> Documentation/git-status.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/git-status.txt b/Documentation/git-status.txt
> index b3319f7..9ec5897 100644
> --- a/Documentation/git-status.txt
> +++ b/Documentation/git-status.txt
> @@ -41,6 +41,15 @@ OPTIONS
> --long::
> Give the output in the long-format. This is the default.
>
> +-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
> + 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`).
> +
> -u[<mode>]::
> --untracked-files[=<mode>]::
> Show untracked files.
next prev parent reply other threads:[~2015-04-23 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-04-23 12:27 ` [PATCH 2/5] git tag: mention versionsort.prereleaseSuffix in manpage Michael Haggerty
2015-04-23 18:28 ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 3/5] RelNotes: correct name of versionsort.prereleaseSuffix Michael Haggerty
2015-04-23 18:29 ` Junio C Hamano
2015-04-23 12:27 ` [PATCH 4/5] RelNotes: refer to the rebase -i "todo list", not "insn sheet" Michael Haggerty
2015-04-23 12:27 ` [PATCH 5/5] RelNotes: wordsmithing Michael Haggerty
2015-04-23 12:47 ` Michael Haggerty
2015-04-23 15:38 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
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
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=xmqqvbgm3dm0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=mhagger@alum$(echo .)mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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