From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86-64/EFI: document building and usage
Date: Wed, 20 Jun 2012 13:02:07 +0100 [thread overview]
Message-ID: <1340193727.4906.52.camel@zakaz.uk.xensource.com> (raw)
In-Reply-To: <4FE1D674020000780008ACA4@nat28.tlf.novell.com>
On Wed, 2012-06-20 at 12:56 +0100, Jan Beulich wrote:
> >>> On 20.06.12 at 13:35, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > On Wed, 2012-06-20 at 08:36 +0100, Jan Beulich wrote:
> >> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> >
> > The text looks fine to me, thanks. One comment inline below.
> >
> > Did you consider using markdown syntax to get a somewhat formatted HTML
> > output? You'd basically just need to s/.txt/.markdown/ and tweak things
> > a bit to use the markdown syntax (which is designed to mostly follow the
> > sorts of ASCII typographical conventions which people use anyway).
> >
> > http://daringfireball.net/projects/markdown/
>
> I didn't consider this, but I can certainly convert it if that's what
> is preferred these days.
I think it's generally preferred for new stuff if the author is willing
(i.e. we'd still rather have .txt than nothing)
> >> +**************************example begin******************************
> >> +[global]
> >> +default=sle11sp2
> >> +
> >> +[sle11sp2]
> >> +options=console=vga,com1 com1=57600 loglvl=all noreboot
> >> +kernel=vmlinuz-3.0.31-0.4-xen ignore_loglevel #earlyprintk=xen
> >> +ramdisk=initrd-3.0.31-0.4-xen
> >> +**************************example end********************************
> >> +
> >> +Other values to specify are
> >
> > As well as "Other values" I think you need to document the ones above as
> > well.
>
> Hmm, I would think anyone half way familiar with Xen can interpret
> the meaning of the four ones used above without extra explanation.
The problem is more those which aren't familiar with Xen who think they
want to deploy it using EFI, for whatever reason.
> I don't intend this small piece of text to be a reference document,
> but just an aid to people (having got tired of individuals contacting
> me namely about how to build xen.efi, despite all the information
> being available already - just scattered around).
Sure. Documenting those three options will help with that too, won't it?
I'd expect that getting pestered by those who can't figure that sort of
thing out would be doubly annoying!
I don't think it'll take more than a line to document each one, a link
to http://xenbits.xen.org/docs/unstable/misc/xen-command-line.html might
be useful too.
next prev parent reply other threads:[~2012-06-20 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 13:03 [PATCH, v2] x86-64/EFI: document building and usage Jan Beulich
2012-06-20 7:36 ` [PATCH] " Jan Beulich
2012-06-20 11:35 ` Ian Campbell
2012-06-20 11:56 ` Jan Beulich
2012-06-20 12:02 ` Ian Campbell [this message]
2012-06-29 16:14 ` Ian Jackson
2012-06-29 16:15 ` [PATCH] x86-64/EFI: document building and usage [and 2 more messages] Ian Jackson
2012-06-20 16:04 ` [PATCH, v2] x86-64/EFI: document building and usage Keir Fraser
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=1340193727.4906.52.camel@zakaz.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.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).