From: Sam Ravnborg <sam@ravnborg.org>
To: Roger Gammans <roger@computer-surgery.co.uk>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: JBD Documentation added in BK-current
Date: Tue, 15 Oct 2002 20:16:48 +0200 [thread overview]
Message-ID: <20021015201648.A3462@mars.ravnborg.org> (raw)
In-Reply-To: <20021014230314.A19801@computer-surgery.co.uk>; from roger@computer-surgery.co.uk on Mon, Oct 14, 2002 at 11:03:15PM +0100
On Mon, Oct 14, 2002 at 11:03:15PM +0100, Roger Gammans wrote:
>
> Well. I'm not surprised there are a few I couldn't find an SGML reference
> for the linuxdoc dtd , or a tutorial when I wrote it, so I guessed by looking
> at other documents and source code.
>
> > [I'm cleaning up the mess in the Makefile after JBD was added right now].
>
> Did I really make it that messy?
The infrastructure in the docbook makefile has changed since 2.4.
Took a look in the journal-api.sgml file, based on the comments you gave.
I had to do a little more to crete .html without warnings.
I've submitted this to Linus and trivial.. as well.
Browsing the resulting file I wonder why there are references to several
jbd files, but they do not include docgen comments.
Are there some patches missing in 2.5 that updates the comments?
Sam
===== Documentation/DocBook/journal-api.tmpl 1.1 vs edited =====
--- 1.1/Documentation/DocBook/journal-api.tmpl Mon Oct 7 16:36:06 2002
+++ edited/Documentation/DocBook/journal-api.tmpl Tue Oct 15 20:06:15 2002
@@ -208,7 +208,7 @@
if you allow unprivileged userspace to trigger codepaths containing these
calls.
-<para>
+</para>
</sect1>
<sect1>
<title>Summary</title>
@@ -244,7 +244,8 @@
}
journal_destroy(my_jrnl);
</programlisting>
-
+</para>
+</sect1>
</chapter>
<chapter id="adt">
next prev parent reply other threads:[~2002-10-15 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 19:23 Sam Ravnborg
2002-10-14 22:03 ` Roger Gammans
2002-10-15 18:16 ` Sam Ravnborg [this message]
2002-10-15 21:38 ` Roger Gammans
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=20021015201648.A3462@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=roger@computer-surgery.co.uk \
/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
all inboxes | Powered by JetHome®