From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] improve error messages in grub-setup
Date: Mon, 4 May 2009 18:23:59 +0200 [thread overview]
Message-ID: <20090504162359.GA17324@thorin> (raw)
In-Reply-To: <1241384553.2442.135.camel@ct>
On Sun, May 03, 2009 at 05:02:33PM -0400, Pavel Roskin wrote:
> > > grub_util_warn() doesn't set any flag that there have been
> > > warnings.
> >
> > That's an option, too. But it would preclude the possibility of issuing
> > warnings for which we don't want to require --force (i.e. lesser evils).
> > I wonder if that would be a problem?
>
> We can decide it when we know what the lesser evils are. I'm fine with
> your patch.
Alright then, I checked it in.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2009-05-04 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 11:15 [PATCH] improve error messages in grub-setup Robert Millan
2009-05-03 4:35 ` Pavel Roskin
2009-05-03 16:55 ` Robert Millan
2009-05-03 17:04 ` Pavel Roskin
2009-05-03 20:54 ` Robert Millan
2009-05-03 21:02 ` Pavel Roskin
2009-05-04 16:23 ` Robert Millan [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=20090504162359.GA17324@thorin \
--to=rmh@aybabtu.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.