From: Markus Elfring <Markus.Elfring@web.de>
To: grub-devel@gnu.org
Subject: Re: Outline menu
Date: Wed, 07 Nov 2007 08:50:23 +0100 [thread overview]
Message-ID: <fgrqo0$p1s$1@ger.gmane.org> (raw)
In-Reply-To: <4730DE0F.9090103@nic.fi>
> I do not fancy XML for the boot loader... and I do not see a need to yet
> another configuration file format for menus. We already have menu
> command that can be used to build menus. Perhaps you can convince me
> otherwise?
I imagine that GRUB can become so flexible that it can be specified which data
formats should be parsed. If the target boot environment has not got enough
resources for XML and XSLT processing, an customised configuration file format
must be used to specify the required menu attributes. Do you know any other
standard file format for outlines that might be more resource-friendly?
Regards,
Markus
next prev parent reply other threads:[~2007-11-07 7:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 19:20 Outline menu Markus Elfring
2007-11-05 15:38 ` Robert Millan
2007-11-05 15:56 ` Vesa Jääskeläinen
2007-11-05 22:01 ` Markus Elfring
2007-11-06 10:01 ` Amin Azez
2007-11-06 21:37 ` Vesa Jääskeläinen
2007-11-07 15:56 ` Amin Azez
2007-11-06 21:35 ` Vesa Jääskeläinen
2007-11-07 7:50 ` Markus Elfring [this message]
2007-11-07 15:44 ` Vesa Jääskeläinen
2007-11-07 19:00 ` Markus Elfring
2007-11-07 19:25 ` Vesa Jääskeläinen
2007-11-08 6:05 ` Markus Elfring
2007-11-08 16:23 ` Vesa Jääskeläinen
2007-11-08 18:15 ` menu attributes Markus Elfring
2007-11-08 18:55 ` Vesa Jääskeläinen
2007-11-08 18:30 ` Improvements for menu display Markus Elfring
2007-11-10 16:19 ` Outline menu Marco Gerards
2007-11-11 8:20 ` Markus Elfring
2007-11-18 11:07 ` Marco Gerards
2007-11-10 16:17 ` Marco Gerards
2007-11-11 8:01 ` Markus Elfring
2007-11-18 11:06 ` Marco Gerards
2007-11-26 10:54 ` software design clarification Markus Elfring
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='fgrqo0$p1s$1@ger.gmane.org' \
--to=markus.elfring@web.de \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.