From: Olaf Hering <olaf@aepfle.de>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH 0/6] docs: convert manpages to pod
Date: Mon, 24 Jul 2017 19:44:17 +0200 [thread overview]
Message-ID: <20170724174416.GC8603@aepfle.de> (raw)
In-Reply-To: <22902.8038.466272.858794@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1642 bytes --]
On Mon, Jul 24, Ian Jackson wrote:
> * There are a lot of other documents in docs/misc/ which are in
> markdown format. Some of them are internal. I'm pretty sure we don't
> want them _all_ converted. So even if you convert the manpages, these
> documents will remain.
I did not intent to change other files outside of docs/man/.
Just the references to non-existant manpages triggered this series.
Sometimes I wish that xen-command-line.5 exists, but google always
helped in such occasions.
> * It may be that there are other markdown processors which could be
> substituted for pandoc - either at runtime or by changing the Xen
> Project's default, upstream.
After a quick research there is a ruby "ronn" and go/ruby "md2man". Both
would have the same dependency issue. Perhaps ruby is less troublesome
because YaST is written in ruby.
> * Our markdown documents are, I think, intended to be plain text which
> can be simply shipped as-is. So for things other than manpages you
> can probably just ship them as if they were text files. If the end
> user wants to read them in a fancy format (eg HTML) they could install
> the relevant processor.
Yes. I have to see what HTML we ship. So far it did not cause trouble.
> * I don't understand why promoting GHC would be a problem. But, in
> the worst case, rather than demoting Xen, you could simply not ship
> certain docs (although - see above about plain text).
The package ghc is in the tree since nearly 5 years, pandoc since 3
years. The hurdle is likely that a 4GB DVD is filled quickly. It is
always a fight to get everyone happy, and ghc is seen as leaf package.
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-24 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 14:14 [PATCH 0/6] docs: convert manpages to pod Olaf Hering
2017-07-24 14:14 ` [PATCH 1/6] docs: add pod variant of xen-pv-channel.7 Olaf Hering
2017-07-24 14:14 ` [PATCH 2/6] docs: add pod variant of xl-network-configuration.5 Olaf Hering
2017-07-24 14:14 ` [PATCH 3/6] docs: add pod variant of xl-numa-placement Olaf Hering
2017-07-24 14:14 ` [PATCH 4/6] docs: remove markdown variant of xen-pv-channel.7 Olaf Hering
2017-07-24 14:14 ` [PATCH 5/6] docs: remove markdown variant of xl-network-configuration.5 Olaf Hering
2017-07-24 14:14 ` [PATCH 6/6] docs: remove markdown variant of xl-numa-placement.7 Olaf Hering
2017-07-24 15:58 ` [PATCH 0/6] docs: convert manpages to pod Ian Jackson
2017-07-24 16:09 ` Olaf Hering
2017-07-24 16:25 ` Ian Jackson
2017-07-24 17:44 ` Olaf Hering [this message]
2017-07-25 9:44 ` Ian Jackson
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=20170724174416.GC8603@aepfle.de \
--to=olaf@aepfle.de \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.