From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel@lists.xenproject.org, pdurrant@amazon.com
Cc: andrew.cooper3@citrix.com, roger.pau@citrix.com,
luwei.kang@intel.com, dwmw@amazon.com
Subject: Re: [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update
Date: Wed, 29 Jan 2020 13:43:30 +0100 [thread overview]
Message-ID: <20200129124330.GG15453@mail-itl> (raw)
In-Reply-To: <20200129123618.1202-1-pdurrant@amazon.com>
[-- Attachment #1.1: Type: text/plain, Size: 349 bytes --]
On Wed, Jan 29, 2020 at 12:36:18PM +0000, Paul Durrant wrote:
> * Linux stub domains (RFC v2)
> - Marek Marczykowski-Górecki
There is v4 series already.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-29 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 12:36 [Xen-devel] [ANNOUNCE] Xen 4.14 Development Update Paul Durrant
2020-01-29 12:43 ` Marek Marczykowski-Górecki [this message]
2020-01-29 12:57 ` Durrant, Paul
2020-01-29 12:47 ` Jan Beulich
2020-01-29 13:00 ` Durrant, Paul
2020-01-29 12:59 ` Jürgen Groß
2020-01-29 13:04 ` David Woodhouse
2020-01-29 14:12 ` Tamas K Lengyel
2020-01-29 18:03 ` Andrew Cooper
-- strict thread matches above, loose matches on Subject: below --
2020-02-26 10:03 Paul Durrant
2020-03-25 10:19 paul
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=20200129124330.GG15453@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=andrew.cooper3@citrix.com \
--cc=dwmw@amazon.com \
--cc=luwei.kang@intel.com \
--cc=pdurrant@amazon.com \
--cc=roger.pau@citrix.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.