All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Gammans <roger@computer-surgery.co.uk>
To: Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org, akpm@zip.com.au
Cc: davej@codemonkey.org.uk
Subject: Re: JBD Documentation added in BK-current
Date: Tue, 15 Oct 2002 22:38:45 +0100	[thread overview]
Message-ID: <20021015223845.A14095@computer-surgery.co.uk> (raw)
In-Reply-To: <20021015201648.A3462@mars.ravnborg.org>; from sam@ravnborg.org on Tue, Oct 15, 2002 at 08:16:48PM +0200

[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]

On Tue, Oct 15, 2002 at 08:16:48PM +0200, Sam Ravnborg wrote:
> 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?

And in 2.4 AFAICT. There is a lot of documentation in the those
c and h files if you look.

The original patch didn;t two thing at once ( bad I know) 
   1 ) split the internal algorithm and public api comments
   2 ) reformat the api comments for docgen.
   
This result in something like 40 extra ps/pdf pages of docs, two
things occur to that there may have been some conflict in the
the .c files when merge due to the time between diff and applying, also
it appears davej passed the file to linux so as small stuff so the docgen
changes prolly need to come throught the ext3 team rather than dave.

If the later is the case it'll prolly fix itself it the fullness as time
as the ext3 team are reviewing the docs.., arent they Andrew??

TTFN
-- 
Roger.
Master of Peng Shui.  (Ancient oriental art of Penguin Arranging)
GPG Key FPR: CFF1 F383 F854 4E6A 918D  5CFF A90D E73B 88DE 0B3E

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2002-10-15 21:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 19:23 JBD Documentation added in BK-current Sam Ravnborg
2002-10-14 22:03 ` Roger Gammans
2002-10-15 18:16   ` Sam Ravnborg
2002-10-15 21:38     ` Roger Gammans [this message]

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=20021015223845.A14095@computer-surgery.co.uk \
    --to=roger@computer-surgery.co.uk \
    --cc=akpm@zip.com.au \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.