From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Felipe Contreras" <felipe.contreras@gmail.com>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: [RFC suggestion] Generate manpage directly with Asciidoctor
Date: Sat, 8 May 2021 11:27:01 +0700 [thread overview]
Message-ID: <5130bb11-002c-9aa9-ac6d-11bfd6f85f3f@gmail.com> (raw)
In-Reply-To: <6095c74993f19_cfc72085d@natae.notmuch>
On 08/05/21 06.03, Felipe Contreras wrote:
>> I think we're better to do like this:
>>
>> * If we're using asciidoc, we will use xmlto
>> * If we're using asciidoctor, we will generate man-pages with
>> asciidoctor directly
>
> This certainly is the way to go.
>
> I'm not sure if Bagas suggested to make USE_ASCIIDOCTOR=YesPlease the
> default, but first we would need to make sure the output without xmlto
> is desirable, which we don't at the moment.
I'm not aiming for defaulting to AsciiDoctor, but I agree that we would like
to migrate away from xmlto by making sure the output sans it is desirable.
> So, even if we were to consider this, *first* the option to use pure
> asciidoctor needs to be in place.
Don't you know there is USE_ASCIIDOCTOR=YesPlease flag which do the job?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-05-08 4:27 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 6:06 [RFC suggestion] Generate manpage directly with Asciidoctor 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5130bb11-002c-9aa9-ac6d-11bfd6f85f3f@gmail.com \
--to=bagasdotme@gmail.com \
--cc=congdanhqx@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.