From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: [PATCH v2 1/3] system_data_types.7: ffix
Date: Thu, 1 Oct 2020 09:37:41 +0200 [thread overview]
Message-ID: <d145931a-3bea-7924-e353-08834cc592f0@gmail.com> (raw)
In-Reply-To: <f9871768-cc7a-fac0-3500-6a0ccaa78099@gmail.com>
Hi Alex, Branden,
On 9/30/20 11:32 PM, Alejandro Colomar wrote:
> Hi Branden & Michael,
>
> On 2020-09-30 12:43, G. Branden Robinson wrote:
> >> However, if using .br is a big headache, I would rather not use
> >> workarounds (as you proposed in an earlier email),
> >> and instead just live with the blank line. It's not much of a
> >> problem.
> >
> > Was an actual decision taken on this? I see patches continuing to roll
> > in containing this .br-based pattern. I think if the extra line is
> > live-withable, it should be lived with (or one of my four proposed
> > alternatives could be used :) ), in preference to setting the bad
> > example of the "naked" .br requests.
>
> No decision yet.
> We continued with the patch,
> considering that we might revert it
> or change it to a different approach in the future.
Yes. I figure we can easily clean up the inconsistency later.
> Actually I thought Michael would have hold the patches until the decision,
I didn't want to slow you down,...
> but he merged them, and it may be easier this way...
> we'll fix it when we decide.
Yes.
> For me, I can live with the extra blank line.
> Michael, what are your thoughts?
I can live with it too.
[...]
>
> >
> > Regards,
> > Branden
> >
> > [1] https://lists.gnu.org/archive/html/groff/2019-03/msg00047.html
> > [2]
> https://gitlab.com/procps-ng/procps/blob/7ac9a0e1f5606696dc799b773d5ec70183ca91a3/ps/ps.1
> >
>
>
> I was writing about the different options and testing them,
> when by accident I discovered that .RS alone, which I introduced lately,
> already fixed the problem we had in the beginning:
> .RS forces a line break after the tag
> (so .br is actually redundant right now).
>
> I guess we'll all be happy with just .RS, right? :-}
I think so.
Cheers,
Michael
PS Alex, I believe we are at a sync point right now (i.e., I think
that I do not have any unprocessed patches from you). Let me know if
I'm wrong.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-10-01 7:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 21:13 [PATCH " Alejandro Colomar
2020-09-27 21:13 ` [PATCH 2/3] system_data_types.7: Add 'FILE' Alejandro Colomar
2020-09-28 6:04 ` Michael Kerrisk (man-pages)
2020-09-28 9:06 ` [PATCH v2 " Alejandro Colomar
2020-09-29 13:15 ` Alejandro Colomar
2020-09-29 13:35 ` Michael Kerrisk (man-pages)
2020-09-27 21:13 ` [PATCH 3/3] FILE.3: New link to system_data_types(7) Alejandro Colomar
2020-09-28 5:59 ` [PATCH 1/3] system_data_types.7: ffix Michael Kerrisk (man-pages)
2020-09-28 9:03 ` [PATCH v2 " Alejandro Colomar
2020-09-28 10:34 ` Michael Kerrisk (man-pages)
2020-09-28 10:37 ` Alejandro Colomar
2020-09-28 11:13 ` G. Branden Robinson
2020-09-28 13:06 ` G. Branden Robinson
2020-09-28 13:44 ` Alejandro Colomar
2020-09-30 10:43 ` G. Branden Robinson
2020-09-30 21:32 ` Alejandro Colomar
2020-10-01 7:37 ` Michael Kerrisk (man-pages) [this message]
2020-10-01 7:52 ` Alejandro Colomar
2020-10-01 9:36 ` Michael Kerrisk (man-pages)
2020-09-28 10:40 ` [PATCH " G. Branden Robinson
2020-09-28 10:51 ` Alejandro Colomar
2020-09-28 12:49 ` G. Branden Robinson
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=d145931a-3bea-7924-e353-08834cc592f0@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).