From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Spah Subject: XE Manpages Date: Tue, 10 Dec 2013 10:26:23 -0800 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6719457968437041894==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============6719457968437041894== Content-Type: multipart/alternative; boundary=047d7b15b21be7690a04ed323fe0 --047d7b15b21be7690a04ed323fe0 Content-Type: text/plain; charset=ISO-8859-1 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 * --047d7b15b21be7690a04ed323fe0 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hey guys,

The XenAPI Admin Pro= ject has been=20 busy writing manpages for the XE command. We currently have some pages=20 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=20 should we store them in the repository? Also, do you guys want the=20 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
<= div> Computer Information Sciences Tutor for Everett Community Col= lege
Network Specialist & Web Admin for the Xenapi Adm= in Project http://xena= piadmin.com
CompTIA Security+ Certified and Cisco CCNA Certified
Arlingt= on, 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
--047d7b15b21be7690a04ed323fe0-- --===============6719457968437041894== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============6719457968437041894==--