All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Pablo Neira <pablo@eurodev.net>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter development mailing list
	<netfilter-devel@lists.netfilter.org>,
	Herve Eychenne <rv@wallfire.org>
Subject: Re: [PATCH 13/18] Netfilter: Multiport revision with port ranges (replaces "mport")
Date: Mon, 10 Jan 2005 13:24:11 +1100	[thread overview]
Message-ID: <1105323851.22093.2.camel@localhost.localdomain> (raw)
In-Reply-To: <41E1B162.2010104@eurodev.net>

On Sun, 2005-01-09 at 23:34 +0100, Pablo Neira wrote:
> 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?

You should add the new feature to the manpage.  The extension should
then fail with an appropriate message if the version of the kernel does
not support the option used.

eg. libipt_MARK.c's "parse_v0" accepts --and-mark (introduced in rev1)
like so:

	case '2':
		exit_error(PARAMETER_PROBLEM,
			   "MARK target: kernel too old for --and-mark");

Cheers,
Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman

  reply	other threads:[~2005-01-10  2:24 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
2005-01-10  2:24           ` Rusty Russell [this message]
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=1105323851.22093.2.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    --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.