All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: grub-devel@gnu.org
Subject: GRUB manual
Date: Fri, 7 Aug 2009 19:28:32 +0200	[thread overview]
Message-ID: <20090807172832.GA13442@thorin> (raw)


Hi,

I've just reviewed the WIP manual in docs/grub.texi, and removed a lot of
information that is specific to GRUB Legacy (sometimes entire sections).

The remaining text was still written with GRUB Legacy in mind, and is
certainly full of inaccuracies related to that.  If you spot one of those,
there's no need to send a patch for review, please shot on sight (but
please make sure you write accurate ChangeLog entries and update
copyright year).

The manual is still not ready for prime use, as some key sections are
missing.  If someone's interested in adding them, I recommend that the
GRUB Legacy manual is checked, as it will surely contain a lot of
reusable text.

If you wish to document new things, please feel free to propose changes,
or to include documentation blurbs in patches that add new functionality
to GRUB.

Also, perhaps it'd be a good idea to build/install the manual in our build
system, with a disclaimer indicating it's not complete or so.  This would
help us gather attention to it and maybe some help, but it can also be
too confusing for users.  Thoughts?

-- 
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."



                 reply	other threads:[~2009-08-07 17:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20090807172832.GA13442@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 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.