From: Jeff King <peff@peff.net>
To: "Андрей Рыбак" <rybak.a.v@gmail.com>
Cc: git@vger.kernel.org, Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Subject: Re: [PATCH] Documentation: make formatting more consistent
Date: Wed, 11 Nov 2015 16:41:06 -0500 [thread overview]
Message-ID: <20151111214106.GA2208@sigill.intra.peff.net> (raw)
In-Reply-To: <CACayv=gEGY-JNfu26fOzztXwhV_bkG8pv_iOXLC5L-Mig9f0kw@mail.gmail.com>
On Wed, Nov 11, 2015 at 06:47:25PM +0300, Андрей Рыбак wrote:
> Documentation/git.txt: enclose all Environment Variables in single quotes.
This tells "what", but we can already see that from the diff. The more
interesting part is "why". Later you say:
> Signed-off-by: Andrey Rybak <rybak.a.v@gmail.com>
> ---
> Documentation/git.txt is not consistent in the way it stylizes mentions
> of Environment Variables. Most of them are enclosed in single quotes,
> some are enclosed in backticks, some are not enclosed.
which I think is the more interesting bit, and should go into the commit
message (but parts after the "---" generally do not). I've grabbed it
manually in this case.
I know we've discussed this particular spot before, and I think there
may have been some disagreement about which style was the best. But
since clearly no patch came out of the last discussion, and since
an inconsistent set of styles is probably worse than consistent use of
any of the choices, this makes sense to me as an incremental step.
If we want to move to all-backticks (for example) later on, we can
easily do so (or we can leave this as the final state).
> diff --git a/Documentation/git.txt b/Documentation/git.txt
> index c2e2a94..900272b 100644
> --- a/Documentation/git.txt
> +++ b/Documentation/git.txt
> @@ -1056,7 +1056,7 @@ of clones and fetches.
> cloning of shallow repositories.
> See 'GIT_TRACE' for available trace output options.
Your patch seems whitespace-damaged (the leading tabs were converted to
spaces). It was pretty easy to fix up in this case, so I did so (i.e.,
no need to re-send), but please check your mailer settings.
Thanks.
-Peff
next prev parent reply other threads:[~2015-11-11 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 15:47 [PATCH] Documentation: make formatting more consistent Андрей Рыбак
2015-11-11 21:41 ` Jeff King [this message]
2015-11-13 5:45 ` Jeff King
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=20151111214106.GA2208@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=rybak.a.v@gmail.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;
as well as URLs for NNTP newsgroup(s).