From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] move functionality of font_path() directly to util/grub-mkconfig.in and prefer unicode.pf2 over ascii.pf2
Date: Sat, 08 Aug 2009 01:12:15 -0400 [thread overview]
Message-ID: <1249708335.28996.21.camel@mj> (raw)
In-Reply-To: <1249649867.3592.11.camel@fz.local>
On Fri, 2009-08-07 at 14:57 +0200, Felix Zielcke wrote:
> I commited it now with an ack from Robert on IRC.
Sorry, I'm commenting after it has been committed. Anyway, please note
that having an approval doesn't absolve you from testing the code on
your own. Reviews are not testing. There was a warning introduced by
your change, and there was a syntax error after "ascii". Also, the
formatting of the moved code should have been changed to use the same
indentation as the target file. I have fixed all that.
Could you please explain what I should do to keep using ascii.pf2? I
checked the script, but don't see any variable controlling that. "make
install" would install both unicode.pf2 and ascii.pf2, so unicode.pf2
would always be preferred.
If changing the default, it's a good style to provide an easy way for
users to keep the old setting, and I just don't see it, short or
removing /usr/src/unifont.bdf and /usr/local/share/grub/unicode.pf2 so
that they are never reinstalled or detected by GRUB.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-08-08 5:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 9:39 [PATCH] move functionality of font_path() directly to util/grub-mkconfig.in and prefer unicode.pf2 over ascii.pf2 Felix Zielcke
2009-08-07 11:39 ` Robert Millan
2009-08-07 12:02 ` Felix Zielcke
2009-08-07 12:57 ` Felix Zielcke
2009-08-08 5:12 ` Pavel Roskin [this message]
2009-08-08 5:36 ` Felix Zielcke
2009-08-08 5:41 ` Felix Zielcke
2009-08-08 5:49 ` Pavel Roskin
2009-08-08 6:04 ` Felix Zielcke
2009-08-08 6:35 ` Pavel Roskin
2009-08-08 6:41 ` 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=1249708335.28996.21.camel@mj \
--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.