From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andrew Beverley <andy@andybev.com>
Cc: Alex Bligh <alex@alex.org.uk>, netfilter@vger.kernel.org
Subject: Re: libnfcontrack weirdness
Date: Mon, 02 Aug 2010 20:45:02 +0200 [thread overview]
Message-ID: <4C57122E.8010108@netfilter.org> (raw)
In-Reply-To: <1280772623.1349.3.camel@andybev>
On 02/08/10 20:10, Andrew Beverley wrote:
> The documentation is sparse, but there are some good examples in the
> utils folder of the source code. Also, api.c is well commented for each
> of the functions.
We should convert that documentation in the source code of api.c to
doxygen format. It shouldn't take more than one hour to get it done.
Then, we can put it on the website as we did for libnetfilter_log and
libnetfilter_queue.
If someone feels in the mood to do it, you can have a look at the other
libraries to see how we've done it.
next prev parent reply other threads:[~2010-08-02 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 16:20 libnfcontrack weirdness Alex Bligh
2010-08-02 18:10 ` Andrew Beverley
2010-08-02 18:45 ` Pablo Neira Ayuso [this message]
2010-08-02 19:10 ` Jan Engelhardt
2010-08-03 12:43 ` Pablo Neira Ayuso
2010-08-03 14:12 ` Jan Engelhardt
2010-08-02 19:14 ` Andrew Beverley
2010-08-02 22:29 ` Alex Bligh
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=4C57122E.8010108@netfilter.org \
--to=pablo@netfilter.org \
--cc=alex@alex.org.uk \
--cc=andy@andybev.com \
--cc=netfilter@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 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.