All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: mtk.manpages@gmail.com
Cc: "G . Branden Robinson" <g.branden.robinson@gmail.com>,
	linux-man <linux-man@vger.kernel.org>
Subject: Re: Format inline code
Date: Thu, 12 Nov 2020 12:32:53 +0100	[thread overview]
Message-ID: <8a1a4d89-6294-2ceb-4f29-13660dd7b068@gmail.com> (raw)
In-Reply-To: <CAKgNAkjsnu9+rxdLgZ5VzYxjFf_c1Ed0JUQ8=KHkK6Qw9X4B-Q@mail.gmail.com>

Hi Michael,

On 11/8/20 1:22 PM, Michael Kerrisk (man-pages) wrote:
> Hi Alex,
> 
[...]
> 
> Yeah, I've wondered about a conversion to .rst, but so far I'm not
> sure, and also I presume it will take a lot of work.

Interesting

[...]
> 
> So, I am a little bit hesitant about "fix-as-we-go". Possibly, this
> means some pages will never be changed. If we were to make the change,
> my preference would be to do all pages at once. But I am not fixed on
> that idea. Some grepping[1] suggests that the number of pages that
> would need to be changed is around 100. Perhaps fix-as-we-go would be
> feasible...
> 
> I'm still thinking about this one.

I mean: while there are many patches,
we could fix-as-we-go,
and when there are not many patches,
we could grep and fix pages that still use a mix of styles.

BTW, I'm fixing perf_event_open.2, and in the first 1400 lines
there have only been around 20 net additions due to .RS/.RE,
so it's not like a lot of extra markup
(around 1% or 2% extra lines).

Cheers,

Alex

  reply	other threads:[~2020-11-12 11:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 10:19 Format inline code Alejandro Colomar
2020-11-05 11:36 ` Michael Kerrisk (man-pages)
2020-11-05 14:59   ` Alejandro Colomar
2020-11-05 21:37     ` Michael Kerrisk (man-pages)
2020-11-05 22:01       ` Alejandro Colomar
2020-11-06  9:38         ` Alejandro Colomar
2020-11-06 16:00           ` Michael Kerrisk (man-pages)
2020-11-06 16:36             ` Alejandro Colomar
2020-11-08 12:22               ` Michael Kerrisk (man-pages)
2020-11-12 11:32                 ` Alejandro Colomar [this message]
2020-11-12 21:17                 ` Alejandro Colomar
2020-11-13  8:28                   ` G. Branden Robinson
2020-11-13  9:00                     ` Michael Kerrisk (man-pages)
2020-11-13  9:47                       ` G. Branden Robinson
2020-11-13 10:11                         ` Michael Kerrisk (man-pages)
2020-11-13 10:21                       ` Alejandro Colomar
     [not found]                 ` <fbaf2a56-3f2e-e5ce-6ca2-e8f30156947d@gmail.com>
2020-11-12 21:20                   ` Alejandro Colomar
2020-11-12 22:55                     ` [RFC v1] perf_event_open.2: srcfix + ffix Alejandro Colomar
2020-11-13  9:21                       ` Michael Kerrisk (man-pages)
2020-11-13 10:26                         ` Alejandro Colomar
2020-11-13 10:39                           ` Michael Kerrisk (man-pages)

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=8a1a4d89-6294-2ceb-4f29-13660dd7b068@gmail.com \
    --to=colomar.6.4.3@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.