All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herve Eychenne <rv@wallfire.org>
To: Phil Oester <kernel@linuxace.com>
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: Sat, 8 Jan 2005 04:42:05 +0100	[thread overview]
Message-ID: <20050108034205.GK8756@eychenne.org> (raw)
In-Reply-To: <20050108020322.GA11903@linuxace.com>

On Fri, Jan 07, 2005 at 06:03:22PM -0800, Phil Oester wrote:

> On Wed, Jan 05, 2005 at 04:46:54PM +1100, Rusty Russell wrote:

> > > While I agree the above is a useful change, why not also add inversion
> > > to multiport in the process -- as long as you're making a new revision?
> > > Or should that be done in revision 2?

> > If you put it in before 2.6.11 is released, it can go in the current
> > revision, otherwise we want a new one (where do we put the invert
> > flags?).

> OK, how about the below which adds inversion?

> (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?

 Herve

-- 
 _
(°=  Hervé Eychenne
//)
v_/_ WallFire project:  http://www.wallfire.org/

  reply	other threads:[~2005-01-08  3:42 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 [this message]
2005-01-09 22:34         ` Pablo Neira
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=20050108034205.GK8756@eychenne.org \
    --to=rv@wallfire.org \
    --cc=kernel@linuxace.com \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=rusty@rustcorp.com.au \
    /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.