From: "Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
To: chris <tknchris@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Sander Eikelenboom <linux@eikelenboom.it>,
"Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Teo En Ming's Xen, Linux Kernel and Xen 4.2-unstable VGA Passthrough Documentation (Version 1.7 Released)
Date: Fri, 30 Mar 2012 03:10:59 +0800 [thread overview]
Message-ID: <4F74B3C3.4040802@gmail.com> (raw)
In-Reply-To: <CAKnNFz8AdXuz5fmUiOQDAduy0Sez3a=oGL2WHxAuXt=zYcEBRA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1466 bytes --]
On 30/03/2012 03:02, chris wrote:
> Plain text only plz :)
>
> On Thu, Mar 29, 2012 at 11:10 AM, George Dunlap
> <George.Dunlap@eu.citrix.com <mailto:George.Dunlap@eu.citrix.com>> wrote:
>
> On Thu, Mar 29, 2012 at 4:05 PM, Teo En Ming (Zhang Enming)
> <singapore.mr.teo.en.ming@gmail.com
> <mailto:singapore.mr.teo.en.ming@gmail.com>> wrote:
> > I think newbie Xen users would find it useful to have my Xen
> documentation.
> > I have consolidated, centralized, listed out every step and covered
> > everything to get Xen, virtual machines and VGA Passthrough up
> and running.
> > I have also covered a lot of topics, including firewall
> configuration to
> > protect Xen networking.
>
> Then the correct thing to do is either:
> * Put the data into the xen.org <http://xen.org> wiki, or
> * Host the files yourself somewhere.
>
> It's important that we not consume subscribers' bandwidth
> unnecessarily. If you persist in sending pdf attachments, we may have
> to ask the mail admins to block pdf attachments entirely.
>
> -George
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org <mailto:Xen-devel@lists.xen.org>
> http://lists.xen.org/xen-devel
>
>
Dear Chris,
Plain text only would be hard to read without any text formatting.
Thank you very much.
--
Yours sincerely,
Mr. Teo En Ming (Zhang Enming)
Singapore
[-- Attachment #1.2: Type: text/html, Size: 2880 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:[~2012-03-29 19:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 14:26 Teo En Ming's Xen, Linux Kernel and Xen 4.2-unstable VGA Passthrough Documentation (Version 1.7 Released) Teo En Ming (Zhang Enming)
2012-03-29 14:47 ` Sander Eikelenboom
2012-03-29 14:51 ` Heiko Wundram
2012-03-29 15:08 ` chris
2012-03-29 15:16 ` Teo En Ming (Zhang Enming)
2012-03-29 15:05 ` Teo En Ming (Zhang Enming)
2012-03-29 15:10 ` George Dunlap
2012-03-29 15:21 ` Teo En Ming (Zhang Enming)
2012-03-29 15:43 ` Dario Faggioli
2012-03-29 15:58 ` Teo En Ming (Zhang Enming)
2012-03-29 19:02 ` chris
2012-03-29 19:10 ` Teo En Ming (Zhang Enming) [this message]
2012-03-29 19:15 ` chris
2012-03-30 4:12 ` Teo En Ming (Zhang Enming)
2012-03-31 10:57 ` Pasi Kärkkäinen
2012-03-31 12:16 ` chris
2012-03-29 20:56 ` Joseph Glanville
2012-03-30 4:20 ` Teo En Ming (Zhang Enming)
-- strict thread matches above, loose matches on Subject: below --
2012-03-29 14:24 Teo En Ming (Zhang Enming)
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=4F74B3C3.4040802@gmail.com \
--to=singapore.mr.teo.en.ming@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=tknchris@gmail.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).