git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 13 Nov 2015 00:45:05 -0500	[thread overview]
Message-ID: <20151113054505.GA32233@sigill.intra.peff.net> (raw)
In-Reply-To: <20151111214106.GA2208@sigill.intra.peff.net>

On Wed, Nov 11, 2015 at 04:41:06PM -0500, Jeff King wrote:

> 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).

Andrey helpfully dug up that thread off-list:

  http://thread.gmane.org/gmane.comp.version-control.git/267990/

If we want to move to backticks, we probably want to also turn on
MAN_BOLD_LITERAL by default, or it's a step backwards for some folks.

As I was the person who suggested backticks back in that thread, and I
do not want to spend the time myself on figuring out if MAN_BOLD_LITERAL
is safe to use everywhere, I somewhat retract my suggestion.

I've queued this patch as-is for now, but I'd be happy to hear other
opinions, or if people want to dig into the MAN_BOLD_LITERAL thing.

-Peff

      reply	other threads:[~2015-11-13  5:45 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
2015-11-13  5:45   ` Jeff King [this message]

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=20151113054505.GA32233@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).