From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: DOC-DAY: WIP for command line options documentation
Date: Thu, 1 Mar 2012 16:32:08 +0000 [thread overview]
Message-ID: <4F4FA488.6080405@citrix.com> (raw)
In-Reply-To: <20303.41895.228499.149827@mariner.uk.xensource.com>
On 01/03/12 16:28, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] DOC-DAY: WIP for command line options documentation"):
>> A good starting point would be to cut-n-paste that wiki page into the
>> markdown docs and then replace the wiki page with a link to the
>> generated docs at http://xenbits.xen.org/docs . This would be preferable
>> to starting completely from scratch.
> I agree but I'm reluctant to let the best be the enemy of the good.
>
> Perhaps it would be best to commit Andrew Cooper's version into the
> tree and then dump the wiki page into it later if and when someone
> gets around to submitting such a patch ?
>
> Ian.
I got half way through dumping the (relevant parts of) wiki page into my
patch, but got interrupted by a support ticket.
When I have completed that, I will resubmit the patch.
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2012-03-01 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 18:43 DOC-DAY: WIP for command line options documentation Andrew Cooper
2012-02-27 19:27 ` Pasi Kärkkäinen
2012-02-28 9:40 ` Andrew Cooper
2012-02-28 9:47 ` Ian Campbell
2012-02-28 13:34 ` Pasi Kärkkäinen
2012-03-01 16:28 ` Ian Jackson
2012-03-01 16:32 ` Andrew Cooper [this message]
2012-03-01 16:53 ` 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=4F4FA488.6080405@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.