From: Ian Campbell <ian.campbell@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] docs: Support building pdfs from markdown using pandoc
Date: Thu, 5 Jun 2014 14:31:00 +0100 [thread overview]
Message-ID: <1401975060.15729.80.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <1401801228-13796-1-git-send-email-andrew.cooper3@citrix.com>
On Tue, 2014-06-03 at 14:13 +0100, Andrew Cooper wrote:
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Ian Campbell <Ian.Campbell@citrix.com>
> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
Acked + applied.
> ---
> Please rerun autogen as part of committing this patch.
Done.
>
> The Xen command line parameters document is far more useful as an indexed pdf
> than it is as unindexed html webpage.
I moved this sentiment into the commit message proper.
Ian.
prev parent reply other threads:[~2014-06-05 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 13:13 [PATCH] docs: Support building pdfs from markdown using pandoc Andrew Cooper
2014-06-05 13:31 ` Ian Campbell [this message]
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=1401975060.15729.80.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@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 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).