From: Rusty Russell <rusty@rustcorp.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Craig Wilkie <craig@homerjay.homelinux.org>
Subject: Re: [TRIVIAL] [PATCH 1 of 3] Fix errors making Docbook documentation
Date: Fri, 10 Jan 2003 11:50:00 +1100 [thread overview]
Message-ID: <20030110073328.A11712C0DD@lists.samba.org> (raw)
In-Reply-To: Your message of "06 Jan 2003 15:20:10 -0000." <1041866409.17472.25.camel@irongate.swansea.linux.org.uk>
In message <1041866409.17472.25.camel@irongate.swansea.linux.org.uk> you write:
> On Mon, 2003-01-06 at 03:47, Rusty Trivial Russell wrote:
> > From: Craig Wilkie <craig@homerjay.homelinux.org>
> > Documentation/Docbook/kernel-api.tmpl - Remove references to source
> > files which do not contain kernel-doc comments, which caused "errors" in
> > the generated documentation.
>
> Please don't do this. The proper fixes already exist just never got
> merged. Also documentation exists for those files and isnt merged. The
> docbook is not the problem, the pile of other missing bits is
>
> Grab the docbook for those files from 2.4 and also the changes to the
> docbook generator
Too late, Linus took it. Craig, since you're doing Documentation
patches, a forward port would be nice.
Thanks,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-01-10 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 3:47 [TRIVIAL] [PATCH 1 of 3] Fix errors making Docbook documentation Rusty Trivial Russell
2003-01-06 15:20 ` Alan Cox
2003-01-10 0:50 ` Rusty Russell [this message]
2003-01-10 11:53 ` Alan Cox
2003-01-10 17:06 ` Linus Torvalds
2003-01-10 17:40 ` Sam Ravnborg
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=20030110073328.A11712C0DD@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=craig@homerjay.homelinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.