From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Haninger <ahaning@gmail.com>
Cc: Adrian Bunk <bunk@stusta.de>,
"Adam J. Richter" <adam@yggdrasil.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Compiling module-init-tools versions after v3.0
Date: Tue, 09 Aug 2005 14:30:22 +1000 [thread overview]
Message-ID: <1123561822.13481.49.camel@localhost.localdomain> (raw)
In-Reply-To: <105c793f0508081812353a07d3@mail.gmail.com>
On Mon, 2005-08-08 at 21:12 -0400, Andrew Haninger wrote:
> On 8/8/05, Adrian Bunk <bunk@stusta.de> wrote:
> > But this could be better handled in module-init-tools.
> Here's hoping it will be once 3.2 is released.
>
> Thanks again.
>
> -Andy
Thanks for this report! This is the first I've heard of it (Adam CC'd
me, thanks!).
Turns out the "docbook2man" uses the *last* <refentrytitle> as the
output filename, so it was building "modprobe.d.5" instead of
"modprobe.conf.5". As a result, modprobe.conf.5 was always old, even in
the tarball I uploaded for 3.1 (when the second refentrytitle went into
the man page), and every "make" tried to rebuild it.
Release coming,
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-08-09 4:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 22:08 Compiling module-init-tools versions after v3.0 Andrew Haninger
2005-08-08 22:32 ` Adrian Bunk
2005-08-09 1:12 ` Andrew Haninger
2005-08-09 4:30 ` Rusty Russell [this message]
2005-08-09 0:25 ` Ken Moffat
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=1123561822.13481.49.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=adam@yggdrasil.com \
--cc=ahaning@gmail.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox