# Re: [PATCH 1/5] status: document the -v/--verbose option 3 messages from 2015-04-24 to 2015-04-24. Participants: Pete Harlan, Junio C Hamano, Michael Haggerty. Thread: https://gitlist.dev/t/39149 ## Pete Harlan, 2015-04-24 00:27 Subject: Re: [PATCH 1/5] status: document the -v/--verbose option Message-ID: URL: https://gitlist.dev/e/CAM%3Dud8zLDTYUp12BsVjWH5%3D8rg%3DHxbtdBxL2L9x%3D3%2BFQVJBqrQ%40mail.gmail.com ``` Junio writes: > Michael Haggerty writes: > > > Document `git status -v`, including its new doubled `-vv` form. > > > > Signed-off-by: Michael Haggerty > >--- > > 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.) ``` ## Junio C Hamano, 2015-04-24 01:44 Subject: Re: [PATCH 1/5] status: document the -v/--verbose option Message-ID: URL: https://gitlist.dev/e/xmqq4mo62tb9.fsf%40gitster.dls.corp.google.com In-Reply-To: ``` Pete Harlan writes: > Junio writes: >> Michael Haggerty writes: >> >> > Document `git status -v`, including its new doubled `-vv` form. >> > >> > Signed-off-by: Michael Haggerty >> >--- >> >> 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, 2015-04-24 16:46 Subject: Re: [PATCH 1/5] status: document the -v/--verbose option Message-ID: <553A7379.6030408@alum.mit.edu> URL: https://gitlist.dev/e/553A7379.6030408%40alum.mit.edu In-Reply-To: ``` On 04/24/2015 02:27 AM, Pete Harlan wrote: > Junio writes: >> Michael Haggerty writes: >> >>> Document `git status -v`, including its new doubled `-vv` form. >>> >>> Signed-off-by: Michael Haggerty >>> --- >> >> 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 ```