From: Sebastien Peterson-Boudreau <sebastien.peterson.boudreau@gmail.com>
To: dash@vger.kernel.org
Subject: Re: [PATCH] Don't use groff(1) specific string syntax
Date: Sat, 9 May 2026 15:23:01 -0300 [thread overview]
Message-ID: <af97hfhK_nFKtQFY@HQ> (raw)
In-Reply-To: <af6gLe2f_jlMCofg@gondor.apana.org.au>
> I checked the NetBSD code and they replaced these with literals
> instead. Any reason why we can't do the same thing?
As I mentioned, those are listed as "preferred" alternatives in
groff_mdoc(7); I wasn't sure if that document was specific to groff --
other "preferred" suggestions are strings that are unique to groff and
not portable -- therefore my concern was portability, but if NetBSD uses
them, it should be fine (and more readable!)
Thanks,
--
S.
prev parent reply other threads:[~2026-05-09 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 18:53 [PATCH] Don't use groff(1) specific string syntax sebastien peterson boudreau
2026-05-09 2:47 ` Herbert Xu
2026-05-09 18:23 ` Sebastien Peterson-Boudreau [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=af97hfhK_nFKtQFY@HQ \
--to=sebastien.peterson.boudreau@gmail.com \
--cc=dash@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