From: Jeff King <firstname.lastname@example.org> To: "Martin Ågren" <email@example.com> Cc: "brian m. carlson" <firstname.lastname@example.org>, Bagas Sanjaya <email@example.com>, Git Users <firstname.lastname@example.org> Subject: Re: [RFC suggestion] Generate manpage directly with Asciidoctor Date: Tue, 11 May 2021 15:07:19 -0400 [thread overview] Message-ID: <YJrV52HOv0mlbJB1@coredump.intra.peff.net> (raw) In-Reply-To: <CAN0heSp6uw7yqNZLD5w13xJUgnUtgHM0OYw9KQ6Z-FKk+x4OPA@mail.gmail.com> On Tue, May 11, 2021 at 08:45:10PM +0200, Martin Ågren wrote: > > That does make things a little less convenient; Debian stable, for > > instance, still has 1.5.8. It's not too hard to install an updated gem, > > but not quite as nice as using the system package (it also makes things > > weird for building the stable Debian package itself, which would want to > > rely only on other packages; but of course any proposed change to the > > doc toolchain would be for new versions, and would not get backported > > there anyway). > > Right. And 1.5.8 is perfectly fine for ascidoctor *with* xmlto, i.e., as > long as we're discussing moving away from asciidoc, not moving away from > xmlto entirely. And soon enough, Debian stable should be at 2.12. ;-) > (I realize Debian stable was just an example.) Debian stable is just an example, but I also consider it a bit of a benchmark for "reasonable". Surely there are people running RHEL6 somewhere in this world, but it's hard to care too much about them. I think the transition you're proposing would probably take a while to do, too. If we don't drop the python asciidoc support until close to the end, then that buys a bit more time. Likewise, this isn't a hard limit for OS support for users. The worst case is just making things slightly more inconvenient for Git developers on older systems, because because they might have to install an updated gem rather than using the system package (you sometimes can end up in dependency hell for a gem upgrade with versions of ruby, system libraries, etc, but I haven't found asciidoctor particularly needy in that respect). So I dunno. I certainly don't have a big complaint about _starting_ the transition. If we can hold on to python asciidoc support (or even old-asciidoctor + xmlto) for a while as a fallback, even if we know it's slowly bitrotting, then it's possible nobody would even complain. -Peff
next prev parent reply other threads:[~2021-05-11 19:07 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-07 6:06 Bagas Sanjaya 2021-05-07 12:02 ` Randall S. Becker 2021-05-07 22:55 ` Felipe Contreras 2021-05-07 22:57 ` brian m. carlson 2021-05-08 1:42 ` Randall S. Becker 2021-05-07 12:27 ` Đoàn Trần Công Danh 2021-05-07 12:47 ` Bagas Sanjaya 2021-05-07 23:03 ` Felipe Contreras 2021-05-08 4:27 ` Bagas Sanjaya 2021-05-07 20:25 ` brian m. carlson 2021-05-07 22:19 ` Jeff King 2021-05-08 4:22 ` Bagas Sanjaya 2021-05-09 8:20 ` Martin Ågren 2021-05-09 18:46 ` Felipe Contreras 2021-05-10 18:43 ` Martin Ågren 2021-05-10 22:24 ` Jeff King 2021-05-11 4:27 ` Felipe Contreras 2021-05-11 6:13 ` Jeff King 2021-05-11 8:03 ` Felipe Contreras 2021-05-11 12:44 ` Ævar Arnfjörð Bjarmason 2021-05-11 19:00 ` Felipe Contreras 2021-05-11 19:09 ` Jeff King 2021-05-11 20:22 ` Felipe Contreras 2021-05-11 23:14 ` brian m. carlson 2021-05-12 1:44 ` Felipe Contreras 2021-05-11 18:45 ` Martin Ågren 2021-05-11 19:07 ` Jeff King [this message] 2021-05-11 19:11 ` Martin Ågren 2021-05-11 20:14 ` Felipe Contreras 2021-05-11 9:04 ` Jean-Noël Avila 2021-05-11 18:54 ` Martin Ågren 2021-05-07 23:35 ` Felipe Contreras 2021-05-07 23:57 ` brian m. carlson 2021-05-08 3:10 ` Jeff King 2021-05-08 3:23 ` Jeff King 2021-05-09 0:22 ` brian m. carlson 2021-05-09 8:29 ` Martin Ågren 2021-05-07 22:48 ` Felipe Contreras
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YJrV52HOv0mlbJB1@coredump.intra.peff.net \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC suggestion] Generate manpage directly with Asciidoctor' \ /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
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git 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).