From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Julien Grall <julien.grall@arm.com>
Subject: Re: backport docs changes for Xen 4.9.1
Date: Thu, 3 Aug 2017 12:07:55 +0200 [thread overview]
Message-ID: <20170803100755.GD28455@aepfle.de> (raw)
In-Reply-To: <59831044020000780016CDB7@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]
On Thu, Aug 03, Jan Beulich wrote:
> >>> On 01.08.17 at 11:43, <olaf@aepfle.de> wrote:
> > Please backport the following changes for docs/ for the Xen 4.9.1
> > release:
> >
> > aa4eb460bc docs: add pod variant of xl-numa-placement
> > 458df9f374 docs: add pod variant of xl-network-configuration.5
> > 4359b86f31 docs: add pod variant of xen-pv-channel.7
> I'm not convinced these qualify for backporting. What's the
> justification?
Less paperwork for me, avoids maintaining three patches. And it fixes the
references within man pages for those who have no pandoc while building
Xen. Not sure if that is just SUSE.
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-08-03 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 9:43 backport docs changes for Xen 4.9.1 Olaf Hering
2017-08-01 9:56 ` Julien Grall
2017-08-03 10:00 ` Jan Beulich
2017-08-03 10:07 ` Olaf Hering [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=20170803100755.GD28455@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=xen-devel@lists.xenproject.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 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.