From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: bug-grub
Date: Tue, 05 Aug 2008 09:53:24 +0300 [thread overview]
Message-ID: <4897F8E4.2000304@nic.fi> (raw)
In-Reply-To: <20080804213922.GA11798@thorin>
Robert Millan wrote:
> 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.
>
Why not use it for all GRUB project bugs? Just to get announcements of
them. What I want is to get usage discussion off the list. There is
already help-grub for the user discussions for both GRUB Legacy and GRUB 2.
prev parent reply other threads:[~2008-08-05 6:53 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 ` bug-grub Robert Millan
2008-08-05 6:53 ` Vesa Jääskeläinen [this message]
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=4897F8E4.2000304@nic.fi \
--to=chaac@nic.fi \
--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