From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org, Sam James <sam@gentoo.org>
Subject: groff 1.23.0 stability (was: using the TQ macro)
Date: Sat, 28 Oct 2023 08:13:25 -0500 [thread overview]
Message-ID: <20231028131325.vloorrwewruhy4lq@illithid> (raw)
In-Reply-To: <ZTkvY8egIrf9pcxF@debian>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Hi Alex,
At 2023-10-25T17:08:19+0200, Alejandro Colomar wrote:
> BTW, I just checked and Gentoo still doesn't consider 1.23.0 stable
> enough <https://packages.gentoo.org/packages/sys-apps/groff>. :|
I don't understand that claim. 1.23.x is as stable as it can be; there
have been no point releases. Its behavior is not changing based on the
calendar. I have to assume that there are either changes since 1.22.4
documented in NEWS (and if not, that's probably a bug) that they're
concerned about, or they're worried the broader community hasn't gotten
enough exposure to it yet. repology.org has been sitting at 64
instances of groff 1.23.0 for weeks now; I think pretty much everyone
who's going to adopt it has done so by now.
CCing Sam James (the only Gentoo developer I know by name, because he's
been active some of the same places I have been) in case he can throw
some light on this.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-28 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 14:11 using the TQ macro G. Branden Robinson
2023-10-25 15:08 ` Alejandro Colomar
2023-10-28 13:13 ` G. Branden Robinson [this message]
2023-10-31 4:38 ` groff 1.23.0 stability (was: using the TQ macro) Sam James
2023-10-31 12:13 ` Alejandro Colomar
2023-11-13 23:48 ` Sam James
2023-11-14 0:25 ` Alejandro Colomar
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=20231028131325.vloorrwewruhy4lq@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=sam@gentoo.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