From: Pablo Neira <pablo@eurodev.net>
To: Herve Eychenne <rv@wallfire.org>
Cc: Harald Welte <laforge@netfilter.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Netfilter development mailing list
<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 13/18] Netfilter: Multiport revision with port ranges (replaces "mport")
Date: Sun, 09 Jan 2005 23:34:10 +0100 [thread overview]
Message-ID: <41E1B162.2010104@eurodev.net> (raw)
In-Reply-To: <20050108034205.GK8756@eychenne.org>
bonjour,
Herve Eychenne wrote:
>>(note: didn't update manpage, but then again, wasn't updated with previous
>>changes)
>>
>>
>
>Maybe because no one stated what the manpage policy regarding the
>new revision system would be?...
>When adding every successive revision documentation of every
>match/target to the manpage, wouldn't it become severly bloated in the
>end?
>
>
Hm, I think that the revision infrastructure gives the possibility of
extending a target/match with some kind of interesting features,
something that we couldn't do so far. However, I don't encourage the
release of a new revision every month or something like that.
So, I think that people must have a good reason to extend a
target/match, and in case that this new revision is considered worthy. I
would hold it for quite some time in the SVN repository and after that
push it forward.
If we follow a policy similar to this, the manpages shouldn't get
bloated so much I guess.
--
Pablo
next prev parent reply other threads:[~2005-01-09 22:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 3:35 [PATCH 13/18] Netfilter: Multiport revision with port ranges (replaces "mport") Rusty Russell
2005-01-05 4:30 ` Phil Oester
2005-01-05 5:32 ` Nicolas Bouliane
2005-01-05 5:46 ` Rusty Russell
2005-01-08 2:03 ` Phil Oester
2005-01-08 3:42 ` Herve Eychenne
2005-01-09 22:34 ` Pablo Neira [this message]
2005-01-10 2:24 ` Rusty Russell
2005-01-11 1:47 ` Herve Eychenne
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=41E1B162.2010104@eurodev.net \
--to=pablo@eurodev.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
--cc=rv@wallfire.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.