From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: bug-grub
Date: Mon, 4 Aug 2008 23:39:22 +0200 [thread overview]
Message-ID: <20080804213922.GA11798@thorin> (raw)
In-Reply-To: <87ej5433ic.fsf@xs4all.nl>
On Mon, Aug 04, 2008 at 10:54:19PM +0200, Marco Gerards wrote:
> Hi,
>
> Robert Millan <rmh@aybabtu.com> writes:
>
> [s/bug-grub/grub-devel/]
>
> > What does everyone think?
>
> IIRC Okuji wants to remain using bug-grub for our bugs. If not, we
> should change this IMO.
I'd like to remain using bug-grub for bugs, too. But for GRUB 2 bugs instead
of GRUB Legacy ones.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2008-08-04 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 14:06 bug-grub Robert Millan
2008-07-19 15:58 ` bug-grub Gregg Levine
2008-07-19 20:05 ` bug-grub Robert Millan
2008-08-04 16:19 ` bug-grub Felix Zielcke
2008-08-04 20:54 ` bug-grub Marco Gerards
2008-08-04 21:39 ` Robert Millan [this message]
2008-08-05 6:53 ` bug-grub Vesa Jääskeläinen
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=20080804213922.GA11798@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox