public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Xen IPFire
Date: Fri, 20 Feb 2015 17:32:46 +0100	[thread overview]
Message-ID: <1424449966.17826.266.camel@ipfire.org> (raw)
In-Reply-To: <54E6BB9F.30007@dailydata.net>

[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]

No the paragraph is really great. I would just like to suggest to put in
on a subpage in the xen namespace. I find shorter pages much better
because you can find information much quicker. If you are searching for
something and use the search function the headline will directly lead
you to the right place. You can easier navigate the pages. Especially on
mobile devices. And of course the wiki allows us to use links to
reference to other pages of which we should make heavy use.

-Michael

On Thu, 2015-02-19 at 22:44 -0600, R. W. Rodolico wrote:
> I have added a discussion of paravirt vs HVM under
> http://wiki.ipfire.org/en/virtualization/xen/start
> 
> If you will tell me what you would like tightened up, I will be happy to
> try. I know I am overly verbose.
> 
> Rod
> 
> On 02/19/2015 07:23 PM, Michael Tremer wrote:
> > Hi Rod,
> > 
> > this is a great read. You are sometimes getting a bit too much into
> > detail so that the articles get a bit long. The structure however makes
> > up for that a bit. The most important information is right at the top
> > and you know where to go to.
> > 
> > I move the articles around a bit and fixed the headlines.
> > 
> > On Wed, 2015-02-18 at 01:16 -0600, R. W. Rodolico wrote:
> >> I have created a whole section on virtualization. It is all in English
> >> (sorry).
> >>
> >> If you will start at:
> >> http://wiki.ipfire.org/en/start
> >> and click on the Virtualization entry (bottom entry), I would appreciate
> >> any comments on it. I intend to collect the other virtualization
> >> articles into this one container.
> >>
> >> Markus, I would love to see your article and do what I can to translate
> >> it. I have a friend who speaks/reads/writes German (I don't know how
> >> well), and I can work out some of it.
> > 
> > Well enough for that. I guess Google translate will also help to get the
> > jist out of it for you.
> > 
> >>
> >> Rod
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-02-20 16:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18  7:16 R. W. Rodolico
2015-02-20  1:23 ` Michael Tremer
2015-02-20  4:44   ` R. W. Rodolico
2015-02-20 16:32     ` Michael Tremer [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=1424449966.17826.266.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=documentation@lists.ipfire.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