All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Grub version variable in shell
Date: Sun, 11 Mar 2012 15:07:09 +0100	[thread overview]
Message-ID: <4F5CB18D.9070506@gmail.com> (raw)
In-Reply-To: <4F5CAEBE.3060905@googlemail.com>

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

On 11.03.2012 14:55, Andreas Born wrote:
> In 1.98 there was that export issue, I already mentioned. When opening
> a new context with configfile e.g. variables were exported to the new
> context, but not marked anymore for reexport. So you had to reexport
> them yourself. No way I'm maintaining a workaround for that. 
What do you think of possibility
if [ x$feature_bug1_fixed != xy -o x$feature_bug2_fixed != xy ]; then
   echo "Too old"
   <basic menu>
else
<complete version>
fi

We probably need a feature feature_200_release anyway since it will be
starting point for most of backward compatibility (compatibility is
loose with 1.99).
Perhaps feature_20x_release is the way to go.

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2012-03-11 14:07 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 [this message]
2012-03-11 14:17           ` Andreas Born
2012-03-11 14:20             ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-11 14:58               ` Andreas Vogel
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=4F5CB18D.9070506@gmail.com \
    --to=phcoder@gmail.com \
    --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.