All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: we need a doc too
Date: Mon, 17 Aug 2009 15:12:04 +0200	[thread overview]
Message-ID: <20090817131203.GC32551@thorin> (raw)
In-Reply-To: <5277f7fa0908140213h7ad3691ao847b782ef9b00970@mail.gmail.com>

On Fri, Aug 14, 2009 at 02:43:46PM +0530, J.Bakshi wrote:
> On Fri, Aug 14, 2009 at 1:18 PM, Marco Gerards<mgerards@xs4all.nl> wrote:
> > Hi,
> >
> > "J.Bakshi" <bakshi12@gmail.com> writes:
> >
> >> It is nice to see that grub 1.97 is on its way. Everyone is waiting
> >> for this power pack. But we also need a good doc for it.
> >> The wiki is out-dated.
> >
> > You are completely right.  Do you volunteer to write documentation?
> >
> I am interested to wtite doc for newbies. My previous doc on legacy
> grub can be found at
> http://jbakshi.50webs.com/Linux_tutorial/GRUB/GNU%20GRUB%20simplified.html
> 
> I am curious to write on gfxterm, theme, password protection , hidden
> menu etc . To do this I need more and more info

We need help with the manual.  There are no GRUB Legacy-specific sections
anymore, but critical parts are missing.  Can you help with that?

-- 
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-17 13:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14  5:05 we need a doc too J.Bakshi
2009-08-14  7:48 ` Marco Gerards
2009-08-14  9:13   ` J.Bakshi
2009-08-17 13:12     ` Robert Millan [this message]
2009-08-17 15:01       ` J. Bakshi

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=20090817131203.GC32551@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.