From: Thomas Schwinge <tschwinge@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: user-defined hooks
Date: Wed, 13 Dec 2006 14:18:32 +0100 [thread overview]
Message-ID: <20061213131832.GF19641@fencepost> (raw)
In-Reply-To: <1164916758.4067.63.camel@diesel>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
Hello!
On Thu, Nov 30, 2006 at 01:59:18PM -0600, Hollis Blanchard wrote:
> Defining the set of useful hooks, the arguments passed to each, and
> documenting them will be critical. Also, just like with commands, once
> we implement a hook we can't remove or change it without breaking config
> files.
True, unless you apply some sort of versioning to the config files. I'm
not directly advocating to do that for GRUB, though. But it'd be an
idea.
Regards,
Thomas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-13 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 19:00 grub2 accessibility: beeps Hollis Blanchard
2006-11-30 19:50 ` Marco Gerards
2006-11-30 19:59 ` user-defined hooks Hollis Blanchard
2006-12-13 13:18 ` Thomas Schwinge [this message]
2006-12-02 17:15 ` grub2 accessibility: beeps Yoshinori K. Okuji
2006-12-04 20:40 ` Marco Gerards
2006-12-05 20:02 ` Yoshinori K. Okuji
2006-12-13 12:45 ` Marco Gerards
2006-12-13 21:38 ` Yoshinori K. Okuji
2006-12-01 15:05 ` tgingold
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=20061213131832.GF19641@fencepost \
--to=tschwinge@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.