From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub 1 troubleshooting, linux boot delayed problem
Date: Sat, 12 Jun 2004 18:11:15 +0200 [thread overview]
Message-ID: <87hdtgwycc.fsf@marco.marco-g.com> (raw)
In-Reply-To: <200406111615.56874.okuji@enbug.org> (Yoshinori K. Okuji's message of "Fri, 11 Jun 2004 16:15:56 +0200")
"Yoshinori K. Okuji" <okuji@enbug.org> writes:
> Your question is irrevalent with this list. Read the manual and/or the
> web site for information on where to use.
>
> ... Why do people send questions to this list again and again? Is it so
> unclear?
And I asked myself the same question several times.
How about these possible causes:
- The GRUB 2 section is the first that appears. When looking for a
mailinglist it is the first list that appears.
- Perhaps it's how people think. If you have to choose between
bug-grub or grub-devel, what would you choose? I would first figure
out what would be the right list, but it seems people don't do this.
- `GRUB Legacy is no longer under development. This means GRUB Legacy
is soon to become abandoned and the only modifications made to it
will be in regards to bug fixes.' That sounds like it is an
abandoned, old version no one uses. I think many people don't know
or care which version they use.
I will think about how to change this later this week and propose a
solution (+patch).
--
Marco
next prev parent reply other threads:[~2004-06-12 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 8:48 Grub 1 troubleshooting, linux boot delayed problem David Balazic
2004-06-11 13:20 ` P
2004-06-11 14:15 ` Yoshinori K. Okuji
2004-06-12 16:11 ` Marco Gerards [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 13:29 David Balazic
2004-06-11 14:30 David Balazic
2004-06-11 14:56 ` Yoshinori K. Okuji
2004-06-12 10:55 David Balazic
2004-06-14 6:33 David Balazic
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=87hdtgwycc.fsf@marco.marco-g.com \
--to=metgerards@student.han.nl \
--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.