From: Matthew Spah <spahmatthew@gmail.com>
To: xen-devel@lists.xen.org
Subject: XE Manpages
Date: Tue, 10 Dec 2013 10:26:23 -0800 [thread overview]
Message-ID: <CAOqsdi6HCev4jKLOKwz0UrSoycGaVC7CWbZsmv-UWKbACemgFw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1177 bytes --]
Hey guys,
The XenAPI Admin Project has been busy writing manpages for the XE command.
We currently have some pages in the xen-api repository (
https://github.com/xapi-project/xen-api/tree/master/docs/en/man/man1). Keep
in mind these pages are not rendered in the manpage format.
I'm looking for guidance on incorporating these into the SPEC file used in
building the xen-api.
How should we go about this? Do we want to list each page in the SPEC file?
Eventually there will be 300+ pages, that could be very tedious. Where
should we store them in the repository? Also, do you guys want the source
code and rendered pages in the repository?
We currently render the pages uses a2x and a custom style sheet.
--
- Matthew Spah
*Implementation Engineer* for Coalfire Systems Inc
*Computer Information Sciences* *Tutor* for Everett Community College
*Network Specialist & Web Admin* for the Xenapi Admin Project
http://xenapiadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlington, WA Cell 425-319-8676
*"What if everything around you. Isn't quite as it seems?" - **Trent Reznor*
*"Experience is the name everyone gives to their mistakes." -- Oscar Wilde *
[-- Attachment #1.2: Type: text/html, Size: 1776 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2013-12-10 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 18:26 Matthew Spah [this message]
2013-12-11 10:03 ` XE Manpages Ian Campbell
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=CAOqsdi6HCev4jKLOKwz0UrSoycGaVC7CWbZsmv-UWKbACemgFw@mail.gmail.com \
--to=spahmatthew@gmail.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 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 NNTP newsgroup(s).