From: Andreas Vogel <Andreas.Vogel@anvo-it.de>
To: grub-devel@gnu.org
Subject: Re: Grub version variable in shell
Date: Sun, 11 Mar 2012 15:58:56 +0100 [thread overview]
Message-ID: <4F5CBDB0.60903@anvo-it.de> (raw)
In-Reply-To: <4F5CB4C1.4070400@gmail.com>
Am 11.03.2012 15:20, schrieb Vladimir 'φ-coder/phcoder' Serbinenko:
> On 11.03.2012 15:17, Andreas Born wrote:
>> Yes, that would be fine with me too. I thought about that too, but
>> actually I didn't quite see the difference between this and
>> grub_version or grub_version_min.
>> Maybe there could be:
>> - feature_200_release: or whatever the version is if somebody
>> really only wants to test/support that one version
>> - feature_20x_release: or whatever appropriate for a series of
>> releases where it's possible to be backwards compatible
>>
> feature_*_release wouldn't be removed for the next release.
The feature_* variables are great. Anyway I support Andreas suggestion
having a GRUB version variable (like many other interpreters/shells are
using it, e.g. BASH, Perl, TCL).
BASH is using 2 variables for it: BASH_VERSION and BASH_VERSINFO. The
second one provides an easy way to get the version, sub-version, etc.
(and eliminates the problems with parsing Andreas was mentioning
before). GRUB could provide something similar, but that's just a thought
which came up right now.
next prev parent reply other threads:[~2012-03-11 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 2:40 Grub version variable in shell Andreas Born
2012-03-11 2:51 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 11:52 ` Andreas Born
2012-03-11 12:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 13:55 ` Andreas Born
2012-03-11 14:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 14:17 ` Andreas Born
2012-03-11 14:20 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 14:58 ` Andreas Vogel [this message]
2012-03-11 21:13 ` Seth Goldberg
2012-03-11 12:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 14:39 ` Andreas Vogel
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=4F5CBDB0.60903@anvo-it.de \
--to=andreas.vogel@anvo-it.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.