All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] improve error messages in grub-setup
Date: Sun, 03 May 2009 17:02:33 -0400	[thread overview]
Message-ID: <1241384553.2442.135.camel@ct> (raw)
In-Reply-To: <20090503205429.GA8753@thorin>

On Sun, 2009-05-03 at 22:54 +0200, Robert Millan wrote:
> On Sun, May 03, 2009 at 01:04:33PM -0400, Pavel Roskin wrote:
> > On Sun, 2009-05-03 at 18:55 +0200, Robert Millan wrote:
> > 
> > > Agreed.  It's no harm to add --force for users who are stuck in such layouts.
> > > 
> > > Here's a new patch.
> > 
> > I don't see the "force" variable affecting anything in setup() other
> > than output.
> 
> There is, see:
> 
> +  grub_util_warn ("Embedding is not possible.  GRUB can only be installed in this "
> +                 "setup by using blocklists.  However, blocklists are UNRELIABLE and "
> +                 "its use is discouraged.");
> +  if (! force)
> +    grub_util_error ("If you really want blocklists, use --force.");
> 
> The first is always displayed, the latter only when we don't have --force

Sorry, I missed the side effect of grub_util_error().  Never mind.

> > 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.

-- 
Regards,
Pavel Roskin



  reply	other threads:[~2009-05-03 21:02 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 [this message]
2009-05-04 16:23           ` Robert Millan

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=1241384553.2442.135.camel@ct \
    --to=proski@gnu.org \
    --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.