From: Dario Faggioli <dario.faggioli@citrix.com>
To: tutu sky <ooohooo_u@hotmail.com>, Paul Durrant <Paul.Durrant@citrix.com>
Cc: "Xen-devel@lists.xen.org" <Xen-devel@lists.xen.org>
Subject: Re: Xen does not work after changing scheduler's code
Date: Tue, 10 May 2016 11:42:07 +0200 [thread overview]
Message-ID: <1462873327.4858.36.camel@citrix.com> (raw)
In-Reply-To: <HE1PR05MB1308302829F2FF5C9C44C2DD8D710@HE1PR05MB1308.eurprd05.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1463 bytes --]
On Tue, 2016-05-10 at 08:47 +0000, tutu sky wrote:
> From: Paul Durrant <Paul.Durrant@citrix.com>
> > From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf
> > Of
> > tutu sky
> >
> > Thanks.
> > would you please tell me what do you mean by top-post?
> Top google hit for 'top post': https://en.wikipedia.org/wiki/Posting_
> style
>
> thanks, it was not intentionally. I hope this message be correct in
> bottom-post format.
> please give me a feedback in order to learn.
>
It is better.
But you should also trim the quotes of the message you are replying to.
Basically, when you write something in your email that is "responding"
to something, things should look... well... like I am making them look
right here.
So, basically, your replies should go _below_ what you are replying to
(and this you've done correct), but you also should remove the parts
that are not necessary (and this, you didn't do at all).
Again, look at what I've done in this mail. Actually, check your
archive of this mailing list (or the web version of those), and you'll
find a lot of examples.
> Thank you in advance.
>
You're welcome. Hope it helps.
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: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-10 9:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 7:48 Xen does not work after changing scheduler's code tutu sky
2016-04-22 8:03 ` Juergen Gross
2016-04-22 8:18 ` tutu sky
2016-04-22 8:46 ` Juergen Gross
2016-04-22 8:59 ` tutu sky
2016-04-26 13:10 ` Dario Faggioli
2016-04-27 14:58 ` tutu sky
2016-04-27 15:21 ` Dario Faggioli
2016-04-27 17:17 ` tutu sky
2016-04-28 8:32 ` George Dunlap
2016-04-28 10:46 ` tutu sky
2016-05-09 14:56 ` George Dunlap
2016-05-10 6:44 ` tutu sky
2016-05-10 8:34 ` Paul Durrant
2016-05-10 8:47 ` tutu sky
2016-05-10 9:42 ` Dario Faggioli [this message]
2016-05-10 9:45 ` Dario Faggioli
2016-05-10 10:02 ` tutu sky
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=1462873327.4858.36.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Xen-devel@lists.xen.org \
--cc=ooohooo_u@hotmail.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 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).