linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Adrian Bunk <bunk@fs.tum.de>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	"David S. Miller" <davem@redhat.com>,
	netfilter-devel@lists.netfilter.org,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [2.4 patch] netfilter Configure.help cleanup
Date: Fri, 25 Jul 2003 22:50:24 +0200	[thread overview]
Message-ID: <20030725205024.GA3244@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20030718012910.0D5BB2C5A9@lists.samba.org>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

On Fri, Jul 18, 2003 at 11:06:49AM +1000, Rusty Russell wrote:
> In message <20030717201304.GL1407@fs.tum.de> you write:
>
> > the patch below does the following changes to the netfilter entries in
> > Configure.help in 2.4.22-pre2:
> > - order similar to net/ipv4/netfilter/Config.in
> > - remove useless short descriptions above CONFIG_*
> > - added CONFIG_IP_NF_MATCH_RECENT entry (stolen from 2.5)
> 
> Sorry Adrian, I think this is overzealous.
> 
> Please just add the CONFIG_IP_NF_MATCH_RECENT entry.  Remember,
> "stable" means "boring". 8)

I will submit the RECENT entry to davem with my next set of patches.

Does everybody else have an ordered Configure.help?  if yes, I'd accept
the patch to comply with common practice.  If not, I would just say: who
cares about the order, it's processed by {old,menu,x}config anyway.

> Rusty.

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-25 20:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-27 23:33 [2.4 patch] netfilter Configure.help cleanup Adrian Bunk
2003-06-30  4:38 ` Rusty Russell
2003-07-02 19:25   ` Marcelo Tosatti
2003-07-17 20:13     ` Adrian Bunk
2003-07-17 20:19       ` David S. Miller
2003-07-18  1:06       ` Rusty Russell
2003-07-25 20:50         ` Harald Welte [this message]
2003-07-26 10:50           ` Adrian Bunk
2003-07-17 20:11   ` Adrian Bunk

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=20030725205024.GA3244@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=bunk@fs.tum.de \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --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 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).