From: Martin Waitz <tali@admingilde.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/4] DocBook: allow to mark structure members private
Date: Tue, 8 Nov 2005 08:25:35 +0100 [thread overview]
Message-ID: <20051108072535.GN9633@admingilde.org> (raw)
In-Reply-To: <20051107194044.1841277b.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
hoi :)
On Mon, Nov 07, 2005 at 07:40:44PM -0800, Randy.Dunlap wrote:
> Just to be clear about the usage, the kernel-doc script switches from
> public to private upon seeing a /*-style comment with the strings
> "private:" or "public:" in it. Right?
exactly.
For now I only changed those comments that already made it clear
what was private and public. Feel free to add more private fields! :-)
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-11-08 7:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 22:54 [patch 0/4] DocBook generation updates Martin Waitz
2005-11-07 22:54 ` [patch 1/4] DocBook: allow to mark structure members private Martin Waitz
2005-11-08 3:40 ` Randy.Dunlap
2005-11-08 7:25 ` Martin Waitz [this message]
2005-11-07 22:54 ` [patch 2/4] DocBook: include printk documentation Martin Waitz
2005-11-07 22:54 ` [patch 3/4] DocBook: comment about paper type Martin Waitz
2005-11-07 22:54 ` [patch 4/4] DocBook: revert xmlto use for .ps and .pdf documentation Martin Waitz
2005-11-08 18:35 [patch 1/4] DocBook: allow to mark structure members private Alexey Dobriyan
2005-11-08 18:27 ` Randy.Dunlap
2005-11-08 19:00 ` Alexey Dobriyan
2005-11-08 18:48 ` Randy.Dunlap
2005-11-08 19:26 ` Alexey Dobriyan
2005-11-09 13:31 ` Martin Waitz
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=20051108072535.GN9633@admingilde.org \
--to=tali@admingilde.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.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 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®