From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [OT] made a blog post about grub 1.96+20080724
Date: Thu, 20 Nov 2008 11:20:42 -0500 [thread overview]
Message-ID: <1227198042.10629.6.camel@dv> (raw)
In-Reply-To: <511f47f50811200510w3596865ei4188225038f28b8a@mail.gmail.com>
On Thu, 2008-11-20 at 18:40 +0530, shirish wrote:
> Hi all,
> Made it to the level I could understand
>
> http://flossexperiences.wordpress.com/2008/11/19/jaunty-and-grub2/#more-269
>
> There are 2 issues though which I hope came out as well :-
>
> a. There is absolute lack of documentation about how and what a user
> is supposed to do.
> b. This should not be how an end-user should be doing this. I hope
> there is an emergence of a single or multiple GUI tools which lets
> end-users touch the /etc/init.d/grub and /etc/default/grub files and
> update the boot-loader.
>
> Suggestions, improvements are invited :)
I believe blog posts are not supposed to be reviewed and refined,
especially by the developers. Their time would be better spent on
writing documentation and improving the code.
If you want to participate in the documentation efforts, I suggest that
you have a look at the GRUB wiki: http://grub.enbug.org/
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-11-20 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 9:23 [OT] made a blog post about grub 1.96+20080724 shirish
2008-11-19 9:24 ` shirish
2008-11-20 13:10 ` shirish
2008-11-20 16:20 ` Pavel Roskin [this message]
2008-11-22 17:51 ` Yoshinori K. Okuji
2008-11-23 20:43 ` James Shewey
2008-11-24 20:52 ` shirish
2008-11-24 21:19 ` Pavel Roskin
2008-11-25 4:22 ` shirish
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=1227198042.10629.6.camel@dv \
--to=proski@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.