From: Dario Faggioli <raistlin@linux.it>
To: "Teo En Ming (Zhang Enming)" <singapore.mr.teo.en.ming@gmail.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Sander Eikelenboom <linux@eikelenboom.it>,
	"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: Thu, 29 Mar 2012 17:43:07 +0200	[thread overview]
Message-ID: <1333035787.4668.36.camel@Solace> (raw)
In-Reply-To: <4F747DEA.90509@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1299 bytes --]
On Thu, 2012-03-29 at 23:21 +0800, Teo En Ming (Zhang Enming) wrote:
> I have created only 3 Xen wiki pages recently and somebody edited and
> messed up my Xen wiki pages. I will request Lars Kurth to see if it's
> possible to make my own Xen wiki pages read-only.
>
It's not possible and neither is necessary to make pages read-only. Have
a look here:
 http://wiki.xen.org/wiki?title=Xen_VGA_Passthrough_to_Windows_8_with_Xen_4.2-unstable&action=history
As you see, the wiki preserves the history of what happens to a page, so
you can restore it to whatever status you like, like, e.g., this one:
 http://wiki.xen.org/wiki?title=Xen_VGA_Passthrough_to_Windows_8_with_Xen_4.2-unstable&oldid=2945
And I'm sure you can do that yourself (without bothering Lars) as you're
the author of the page.
> I will not be sending any more emails to xen mailing lists with PDF
> document attachments.
>
That would be great, thanks. :-)
Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-------------------------------------------------------------------
Dario Faggioli, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
PhD Candidate, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 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 15:43 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 [this message]
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)
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=1333035787.4668.36.camel@Solace \
    --to=raistlin@linux.it \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=singapore.mr.teo.en.ming@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).