From: Dario Faggioli <dario.faggioli@citrix.com>
To: Olaf Hering <olaf@aepfle.de>,
xen-devel@lists.xen.org, Ian Jackson <ian.jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH v3 3/3] docs: add pod variant of xl-numa-placement
Date: Thu, 27 Jul 2017 13:46:43 +0200 [thread overview]
Message-ID: <1501156003.25077.5.camel@citrix.com> (raw)
In-Reply-To: <20170726143950.30329-4-olaf@aepfle.de>
[-- Attachment #1.1: Type: text/plain, Size: 645 bytes --]
On Wed, 2017-07-26 at 16:39 +0200, Olaf Hering wrote:
> Convert source for xl-numa-placement.7 from markdown to pod.
> This removes the buildtime requirement for pandoc, and subsequently
> the
> need for ghc, in the chain for BuildRequires of xen.rpm.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
>
Reviewed-by: Dario Faggioli <dario.faggioli@citrix.com>
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 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-27 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 14:39 [PATCH v3 0/3] docs: convert manpages to pod Olaf Hering
2017-07-26 14:39 ` [PATCH v3 1/3] docs: add pod variant of xen-pv-channel.7 Olaf Hering
2017-07-26 14:39 ` [PATCH v3 2/3] docs: add pod variant of xl-network-configuration.5 Olaf Hering
2017-07-26 14:39 ` [PATCH v3 3/3] docs: add pod variant of xl-numa-placement Olaf Hering
2017-07-27 11:46 ` Dario Faggioli [this message]
2017-07-28 14:54 ` [PATCH v3 0/3] docs: convert manpages to pod Wei Liu
2017-09-19 14:36 ` 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=1501156003.25077.5.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--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 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).