From: Eric Leblond <eric@regit.org>
To: Chris Boot <bootc@bootc.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ulog: ulogd.conf.5 man page
Date: Sat, 08 Jun 2013 12:37:02 +0200 [thread overview]
Message-ID: <1370687822.5642.8.camel@ice-age.regit.org> (raw)
In-Reply-To: <51AA46ED.5060208@bootc.net>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
Hello,
Sorry for the late answer.
Le samedi 01 juin 2013 à 20:09 +0100, Chris Boot a écrit :
> 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.
It seems this is the case indeed.
> 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.
I agree that a man page for configuration can be useful but it should be
made from the ulogd.sgml file as there is tool similar to docbook2man
which should be able to do the transformation.
BR,
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2013-06-08 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-01 19:09 ulog: ulogd.conf.5 man page Chris Boot
2013-06-08 10:37 ` Eric Leblond [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=1370687822.5642.8.camel@ice-age.regit.org \
--to=eric@regit.org \
--cc=bootc@bootc.net \
--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).