From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: [PATCH] Clean up dangling references to grub-setup
Date: Mon, 7 Jan 2013 16:01:35 +0400 [thread overview]
Message-ID: <20130107160135.7787866a@opensuse.site> (raw)
In-Reply-To: <20130107105404.GC26167@riva.dynamic.greenend.org.uk>
В Mon, 7 Jan 2013 10:54:04 +0000
Colin Watson <cjwatson@ubuntu.com> пишет:
> On Thu, Jan 03, 2013 at 06:13:11PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> > On 02.01.2013 18:18, Colin Watson wrote:
> >
> > > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1082045 notes a
> > > dangling documentation reference to grub-setup, and I found several
> > > others. This patch cleans them up as best I can manage; it would be a
> > > little better if the .h2m files could contain architecture-specific
> > > substitutions, but I think this is good enough.
> >
> > In general it's better to avoid mentionning grub-*-setup in user docs at
> > all. Such info is inner workings and belongs to dev docs.
>
> OK. How about this?
>
It does "avoid mentioning". It would be nice if it also did "belongs to
dev docs" ...
> 2013-01-07 Colin Watson <cjwatson@ubuntu.com>
>
> * docs/grub.texi (Images): Refer generally to grub-install rather
> than directly to grub-setup.
> (Installing GRUB using grub-install): Remove direct reference to
> grub-setup.
> (Device map) Likewise.
> (Invoking grub-install): Likewise.
> * docs/man/grub-install.h2m (SEE ALSO): Likewise.
> * docs/man/grub-mkimage.h2m (SEE ALSO): Likewise.
> * util/grub-install.in (usage): Likewise.
>
next prev parent reply other threads:[~2013-01-07 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 17:18 [PATCH] Clean up dangling references to grub-setup Colin Watson
2013-01-03 17:13 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-01-07 10:54 ` Colin Watson
2013-01-07 12:01 ` Andrey Borzenkov [this message]
2013-01-07 14:43 ` Colin Watson
2013-01-09 20:56 ` Vladimir 'φ-coder/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=20130107160135.7787866a@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.