All of lore.kernel.org
 help / color / mirror / Atom feed
From: adrian15 <adrian15sgd@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB 2 documentation
Date: Sun, 01 Jul 2007 13:18:59 +0200	[thread overview]
Message-ID: <46878DA3.103@gmail.com> (raw)
In-Reply-To: <a5a1faa10706270617i1b61e721ka05c587cdfe56fe7@mail.gmail.com>

Khaled Hosny escribió:
> I'd like to work on this, any idea where to begin? should I start with
> grub legacy documentation and update/remove/add information to match
> that of grub2 or should I start from scratch?
> 

In my opinnion there are three ways to elaborate documentation.
1) From grub2 developer point of view.
2) From grub2 architecture.
3) From a grub2 user.


	As long as scripting is not well defined I think you can begin with the
grub2 architecture. I think knowing yourself the grub2 architecture can
make things easier when elaborating documentation from a grub2 user
point of view.

	I mean one of the first thing a grub2 documentation from a grub2 user
point of view should have is an introduction on how does grub2 work overall.

adrian15




  reply	other threads:[~2007-07-01 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-26 16:21 GRUB 2 documentation shirish
2007-06-26 17:24 ` Marco Gerards
2007-06-27 13:17   ` Khaled Hosny
2007-07-01 11:18     ` adrian15 [this message]
2007-07-01 11:48     ` Marco Gerards

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=46878DA3.103@gmail.com \
    --to=adrian15sgd@gmail.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 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.