From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Jordi Mallach <jordi@sindominio.net>
Subject: Re: [PATCH] Build info documentation
Date: Sat, 19 Sep 2009 23:14:49 +0200 [thread overview]
Message-ID: <20090919211449.GC16223@thorin> (raw)
In-Reply-To: <20090915052012.GU13423@riva.ucam.org>
Excellent. This was much needed.
On Tue, Sep 15, 2009 at 06:20:13AM +0100, Colin Watson wrote:
> I'm not quite sure I've got everything right here, so please review.
My knowledge of texinfo is very limited. Perhaps Jordi will comment on this.
In any case, if nobody objects to it during the weekend, you can commit.
> It seemed much simpler to add everything to Makefile.in than to go
> through conf/*.rmk for this, as there's no platform-specific work to be
> done here.
Seems fine.
--
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."
next prev parent reply other threads:[~2009-09-19 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 5:20 [PATCH] Build info documentation Colin Watson
2009-09-19 21:14 ` Robert Millan [this message]
2009-09-22 7:49 ` Vladimir 'phcoder' Serbinenko
2009-09-23 17:20 ` Colin Watson
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=20090919211449.GC16223@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
--cc=jordi@sindominio.net \
/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.