From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: [PATCH v2] doc: Add missing "-n" (dry-run) option to reflog man page
Date: Wed, 22 Nov 2017 05:45:22 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1711220543450.10299@DESKTOP-1GPMCEJ> (raw)
In-Reply-To: <xmqqy3mysii0.fsf@gitster.mtv.corp.google.com>
On Wed, 22 Nov 2017, Junio C Hamano wrote:
> "Robert P. J. Day" <rpjday@crashcourse.ca> writes:
>
> > i appreciate the need for brevity, but this just takes us back
> > to, is there a standard for man pages, given how they bounce
> > around all over the place?
> >
> > i tossed in that missing "-n" option for "man git-reflog" since
> > it was the *only* option missing from the SYNOPSIS,...
>
> Don't we also take "-v" for "--verbose"?
>
> I am not sure what you meant by "bounce around", but by adding "-n"
> without adding "-v", doesn't this patch worsen the situation by
> making the result even locally inconsistent?
i don't believe "git reflog" supports "-v", only "--verbose", or am
i misreading the source?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2017-11-22 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 15:39 [PATCH v2] doc: Add missing "-n" (dry-run) option to reflog man page Robert P. J. Day
2017-11-22 3:28 ` Junio C Hamano
2017-11-22 7:59 ` Robert P. J. Day
2017-11-22 10:41 ` Junio C Hamano
2017-11-22 10:45 ` Robert P. J. Day [this message]
2017-11-22 16:03 ` 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=alpine.LFD.2.21.1711220543450.10299@DESKTOP-1GPMCEJ \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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