From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATH] grub-mkrelpath
Date: Mon, 02 Nov 2009 16:41:30 +0100 [thread overview]
Message-ID: <1257176490.3299.0.camel@fz.local> (raw)
In-Reply-To: <20091102134529.GA7765@thorin>
Am Montag, den 02.11.2009, 14:45 +0100 schrieb Robert Millan:
> > I wasn't sure if I should do it at the same time or not.
> > The just grub-mkrelpath way has the advantage that if something in
> the
> > function is still broken (which I don't think) then just
> grub-mkrelpath
> > is broken not also grub-probe.
>
> Don't worry, if something is broken it's better to know early about
> it. We
> have experimental branch for safety.
I just pushed the grub-probe change.
Works also for me.
and I also changed the `reading %s via GRUB facilities' info message to
use the grub_path instead of the OS path.
IMO it's more useful then showing twice the same path.
--
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer
next prev parent reply other threads:[~2009-11-02 15:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 12:53 [PATH] grub-mkrelpath Felix Zielcke
2009-08-28 16:28 ` Robert Millan
2009-08-28 17:58 ` Felix Zielcke
2009-08-28 23:55 ` Robert Millan
2009-08-29 0:58 ` Vladimir 'phcoder' Serbinenko
2009-08-29 7:51 ` Felix Zielcke
2009-11-01 15:39 ` Felix Zielcke
2009-11-01 22:04 ` Robert Millan
2009-11-02 8:54 ` Felix Zielcke
2009-11-02 13:45 ` Robert Millan
2009-11-02 15:41 ` Felix Zielcke [this message]
2009-11-03 10:21 ` rubisher
2009-11-03 10:33 ` Felix Zielcke
2009-11-03 13:51 ` rubisher
2009-11-03 14:09 ` Felix Zielcke
2009-11-04 9:55 ` rubisher
2009-11-04 11:07 ` Felix Zielcke
2009-11-04 14:59 ` rubisher
2009-11-04 15:55 ` Felix Zielcke
2009-11-11 22:43 ` Felix Zielcke
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=1257176490.3299.0.camel@fz.local \
--to=fzielcke@z-51.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.