From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] allow user-configurable menucolor
Date: Sun, 6 Jan 2008 00:42:40 +0100 [thread overview]
Message-ID: <20080105234240.GA7078@thorin> (raw)
In-Reply-To: <878x342bg5.wl@dekkers.cx>
On Sat, Jan 05, 2008 at 10:45:46PM +0100, Jeroen Dekkers wrote:
> At Thu, 3 Jan 2008 16:35:33 +0100,
> Robert Millan wrote:
> > diff -x '*~' -x '*.mk' -Nurp grub2/include/grub/normal.h grub2.color/include/grub/normal.h
> > --- grub2/include/grub/normal.h 2007-07-22 01:32:22.000000000 +0200
> > +++ grub2.color/include/grub/normal.h 2008-01-03 16:12:53.000000000 +0100
> > @@ -1,7 +1,7 @@
> > /* normal.h - prototypes for the normal mode */
> > /*
> > * GRUB -- GRand Unified Bootloader
> > - * Copyright (C) 2002,2003,2005,2006,2007 Free Software Foundation, Inc.
> > + * Copyright (C) 2002,2003,2005,2006,2007,2008 Free Software Foundation, Inc.
> > *
> > * GRUB is free software: you can redistribute it and/or modify
> > * it under the terms of the GNU General Public License as published by
> > @@ -154,6 +154,9 @@ grub_err_t grub_normal_print_device_info
> > grub_err_t grub_normal_menu_addentry (const char *title,
> > struct grub_script *script,
> > const char *sourcecode);
> > +char *grub_env_write_color_normal (struct grub_env_var *var, const char *val);
> > +char *grub_env_write_color_highlight (struct grub_env_var *var, const char *val);
> > +void grub_wait_after_message (void);
>
> You should actually also include grub/env.h if you use struct
> grub_env_var in the prototypes.
Uhm, I included it in normal/color.c to satisfy the dependencies:
normal/color.c:#include <grub/env.h>
normal/color.c:grub_env_write_color_normal (struct grub_env_var *var __attribute__ ((unused)),
normal/color.c:grub_env_write_color_highlight (struct grub_env_var *var __attribute__ ((unused)),
but your idea seems better. I suppose we can remove it from there now?
> I've fixed that in CVS.
Thanks.
Btw, nice to see you around here. Do you have any news about the CD-ROM
GSoC ? I looked at the tarball from google.com, but CD access seems
unfinished (I couldn't access the CD neither in qemu nor in real hw).
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call, if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-01-05 23:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 12:47 [PATCH] allow user-configurable menucolor Robert Millan
2008-01-01 13:14 ` Vesa Jääskeläinen
2008-01-01 13:40 ` Robert Millan
2008-01-01 13:51 ` Vesa Jääskeläinen
2008-01-01 14:45 ` Robert Millan
2008-01-01 17:38 ` Robert Millan
2008-01-02 21:48 ` Robert Millan
2008-01-02 23:55 ` Yoshinori K. Okuji
2008-01-03 0:56 ` Robert Millan
2008-01-02 23:42 ` Yoshinori K. Okuji
2008-01-03 1:04 ` Robert Millan
2008-01-03 15:35 ` Robert Millan
2008-01-03 16:04 ` Vesa Jääskeläinen
2008-01-03 16:38 ` Robert Millan
2008-01-23 8:56 ` Marco Gerards
2008-01-04 8:02 ` opening new context (was: [PATCH] allow user-configurable menucolor) Robert Millan
2008-01-05 1:34 ` Yoshinori K. Okuji
2008-01-05 11:49 ` Robert Millan
2008-01-05 12:03 ` Yoshinori K. Okuji
2008-01-05 12:09 ` Robert Millan
2008-01-05 21:45 ` [PATCH] allow user-configurable menucolor Jeroen Dekkers
2008-01-05 23:42 ` Robert Millan [this message]
2008-01-06 11:33 ` Jeroen Dekkers
2008-01-06 12:54 ` 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=20080105234240.GA7078@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.