threads / patch / 39149

patch, 5 partsRe: [PATCH 1/5] status: document the -v/--verbose option

Subject: Re: [PATCH 1/5] status: document the -v/--verbose option

## tl;dr

3 messages between Apr 24, 2015 and Apr 24, 2015. Diffs are folded; open one to read it.

replies: 2people: 3as markdown or json

Pete Harlan· Apr 24, 2015, 00:27 UTC · lore
Junio writes:
Show 10 quoted lines
> 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.
[...]
Show 5 quoted lines
> > +-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.)
Junio C Hamano· Apr 24, 2015, 01:44 UTC · re: Pete Harlan · lore
Pete Harlan <pchpublic88@gmail.com> writes:
Show 29 quoted lines
> 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'.
Michael Haggerty· Apr 24, 2015, 16:46 UTC · re: Pete Harlan · lore
On 04/24/2015 02:27 AM, Pete Harlan wrote:
Show 25 quoted lines
> 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

← back to recent threads