From: Chris Boot <bootc@bootc.net>
To: netfilter-devel@vger.kernel.org, Eric Leblond <eric@regit.org>
Subject: ulog: ulogd.conf.5 man page
Date: Sat, 01 Jun 2013 20:09:33 +0100 [thread overview]
Message-ID: <51AA46ED.5060208@bootc.net> (raw)
Hi,
As part of my work in packaging ulogd 2.x for Debian, I'd like to write
a man page for the ulogd.conf configuration file. I started out writing
this a few days ago and I have progressed quite well:
https://github.com/bootc/ulogd2/blob/add-ulogd.conf.5-wip/ulogd.conf.5
I'm send this email because as I write, I realise I'm either repeating
or replacing (by augmentation) quite a bit of the content in the
ulogd.sgml file. Before I sink quite a few more hours into fleshing out
the file, I wanted to check whether I'm going in the right direction and
whether/how I need to change what I'm doing to have the work accepted
upstream.
I think a man page will be very useful to have - I often find myself
reaching for them - I just want to know if I'm going about it from
completely the wrong angle.
Thanks,
Chris
--
Chris Boot
bootc@bootc.net
next reply other threads:[~2013-06-01 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 19:09 Chris Boot [this message]
2013-06-08 10:37 ` ulog: ulogd.conf.5 man page Eric Leblond
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=51AA46ED.5060208@bootc.net \
--to=bootc@bootc.net \
--cc=eric@regit.org \
--cc=netfilter-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).