From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: [PATCH] bisect: mention "view" as an alternative to "visualize"
Date: Fri, 10 Nov 2017 16:13:46 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1711101609240.6187@localhost.localdomain> (raw)
In-Reply-To: <CAPig+cRtpmtD8XqhdXrn1iWOEf9Yx=TXQB=yvXBZ+uR_+XRcPg@mail.gmail.com>
On Fri, 10 Nov 2017, Eric Sunshine wrote:
> Thanks for the patch. Some comments below...
>
> On Fri, Nov 10, 2017 at 11:32 AM, Robert P. J. Day
> <rpjday@crashcourse.ca> wrote:
> > Tweak a number of files to mention "view" as an alternative to
> > "visualize":
>
> You probably want to end this sentence with a period, not a colon.
not sure about that, what's the standard when you're introducing a
code snippet?
> > Documentation/git-bisect.txt | 9 ++++-----
> > Documentation/user-manual.txt | 3 ++-
> > builtin/bisect--helper.c | 2 +-
> > contrib/completion/git-completion.bash | 2 +-
> > git-bisect.sh | 4 ++--
> > 5 files changed, 10 insertions(+), 10 deletions(-)
>
> The diffstat belongs below the "---" separator, otherwise this text
> will (undesirably) become part of the commit message proper.
no, i actually want that as part of the commit message. my standard
is, if there are 5 or more files that get changed, i like to include a
diff --stat in the commit message so people viewing the log can get a
quick idea of how much has changed. if that's not desired here, i can
remove it.
> > + git bisect visualize|view
>
> I think you need parentheses around these terms (see "git bisect
> skip", for example):
>
> git bisect (visualize | view)
ah, quite so.
> However, in this case, it might be easier for readers if each is
> presented on its own line (and subsequent discussion can make it clear
> that they are synonyms).
>
> git bisect visualize
> git bisect view
>
> But, that's a matter of taste...
given the precedent already established:
git bisect (bad|new|<term-new>) [<rev>]
git bisect (good|old|<term-old>) [<rev>...]
i'll go with the parentheses and no intervening spaces. i'll let that
posting simmer for a bit longer before posting "v2".
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-10 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 16:32 [PATCH] bisect: mention "view" as an alternative to "visualize" Robert P. J. Day
2017-11-10 21:06 ` Eric Sunshine
2017-11-10 21:13 ` Robert P. J. Day [this message]
2017-11-10 22:08 ` Eric Sunshine
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.1711101609240.6187@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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