From: Felipe Contreras <firstname.lastname@example.org> To: Jeff King <email@example.com>, Felipe Contreras <firstname.lastname@example.org> Cc: "Ævar Arnfjörð Bjarmason" <email@example.com>, "Martin Ågren" <firstname.lastname@example.org>, "brian m. carlson" <email@example.com>, "Bagas Sanjaya" <firstname.lastname@example.org>, "Git Users" <email@example.com> Subject: Re: [RFC suggestion] Generate manpage directly with Asciidoctor Date: Tue, 11 May 2021 15:22:23 -0500 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <YJrWXfmaNVIL/TzT@coredump.intra.peff.net> Jeff King wrote: > On Tue, May 11, 2021 at 02:00:55PM -0500, Felipe Contreras wrote: > > > > > > 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). > > > > Doing `gem install` solves the problem for whomever wants to build the > > latest git in Debian stable. > > > > Building Debian stable packages is something else. > > Perhaps I wasn't clear with the "but of course" part of my statement. It > was meant to rebut the earlier half of the parenthetical. I.e., drawing > that same distinction as "we don't have to worry about packaging Debian > stable here". Ah, I undesrstood wrong there, it seems we are in agreement. Semicolons in English are similar to semicolons in computer languages: when I read ($a; $b), $a needs to stand on its own. If $b is really important I would do ($a, but $b). But this is like splitting hairs of splitted hairs. I've seen too much discussion and too few patches, I'll send the mockup I did a few days ago to see if it sticks. Cheers. -- Felipe Contreras
next prev parent reply other threads:[~2021-05-11 20:22 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 [this message] 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 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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).