From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub-mkimage and other utils documentation
Date: Tue, 26 Nov 2013 21:35:22 +0400 [thread overview]
Message-ID: <20131126213522.22e8fd48@opensuse.site> (raw)
In-Reply-To: <CADtfRCVijViJ2kXw2Wo5WbX19QttWDdZWVFXSr91LkkkBQauYA@mail.gmail.com>
В Tue, 26 Nov 2013 09:02:09 -0800
Jonathan McCune <jonmccune@google.com> пишет:
> On Tue, Nov 26, 2013 at 8:40 AM, Andrey Borzenkov <arvidjaar@gmail.com>wrote:
>
> > I started to clean --pubkey in docs, hit grub-mkimage reference, hit
> > "grub-install is just a shell script" ... it really needs cleanup.
>
>
> I think the grub-mkimage reference can be dropped now that the native-code
> grub-install is in place and supports --pubkey itself.
It is far more than --pubkey. grub-install section itself starts with
reference to grub-mkimage.
> Sorry, at the time
> those were written it was hard not to reveal some internals. Thanks for
> taking the initiative to clean them up.
>
> -Jon
>
>
>
> > Is
> > grub-install terse description intentional? If not, I'm going to
> > actually document all utilities and all options not defined as hidden.
> > We probably need to mention common options between various utilities
> > as well.
> >
> > Or should some tools be skipped? I'm fine to document them in
> > grub-devel though, but I'd like to have them documented /somewhere/.
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > https://lists.gnu.org/mailman/listinfo/grub-devel
> >
next prev parent reply other threads:[~2013-11-26 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 16:40 grub-mkimage and other utils documentation Andrey Borzenkov
2013-11-26 17:02 ` Jonathan McCune
2013-11-26 17:35 ` Andrey Borzenkov [this message]
2013-11-26 17:16 ` Bruce Dubbs
2013-11-28 6:37 ` Vladimir 'phcoder' Serbinenko
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=20131126213522.22e8fd48@opensuse.site \
--to=arvidjaar@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.