public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: netfilter - Remove netfilter and netfilter-core lists
Date: Mon, 11 Jan 2010 12:14:14 +0100	[thread overview]
Message-ID: <4B4B0806.40801@trash.net> (raw)
In-Reply-To: <1263208183.1907.50.camel@Joe-Laptop.home>

Joe Perches wrote:
> On Mon, 2010-01-11 at 11:51 +0100, Patrick McHardy wrote:
>> it's enough to CC netfilter-devel and optionally
>> netdev on patches, netfilter and netfilter-core are unnecessary.
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 745643b..860d04f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3742,8 +3742,6 @@ P:	Harald Welte
>  P:	Jozsef Kadlecsik
>  M:	Patrick McHardy <kaber@trash.net>
>  L:	netfilter-devel@vger.kernel.org
> -L:	netfilter@vger.kernel.org
> -L:	coreteam@netfilter.org

A comment stating the purpose of each list would be more approriate IMO.
netfilter-devel is for developers and patches, netfilter is for users
and netfilter-core is only meant to reach the coreteam privately.

  reply	other threads:[~2010-01-11 11:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06  1:20 [PATCH 0/8] Remove most uses of NIPQUAD and NIPQUAD_FMT Joe Perches
2010-01-06  1:20 ` [PATCH 1/8] drivers/scsi: Remove uses of NIPQUAD, use %pI4 Joe Perches
2010-01-06  1:20 ` [PATCH 2/8] drivers/staging/pohmelfs/inode.c: " Joe Perches
2010-01-06  1:20 ` [PATCH 3/8] net/rds: " Joe Perches
2010-01-06  1:20 ` [PATCH 4/8] net/sunrpc: " Joe Perches
2010-01-06  1:20 ` [PATCH 5/8] net/ipv4/netfilter/nf_nat_ftp.c: Convert NIPQUAD to %pI4 Joe Perches
2010-01-06 19:23   ` [PATCH v2 5/8] net/ipv4/netfilter/nf_nat_ftp.c: Remove (*mangle[]) array and functions, use %pI4 Joe Perches
2010-01-11 10:51     ` Patrick McHardy
2010-01-11 11:09       ` [PATCH] MAINTAINERS: netfilter - Remove netfilter and netfilter-core lists Joe Perches
2010-01-11 11:14         ` Patrick McHardy [this message]
2010-01-11 11:27           ` [PATCH V2] MAINTAINERS: netfilter - Document netfilter and netfilter-core lists purposes Joe Perches
2010-01-11 11:31             ` Jan Engelhardt
2010-01-11 11:43               ` Joe Perches
2010-01-12 18:46               ` [PATCH V3] MAINTAINERS: Document list types, add "A:" section type, update NETFILTER Joe Perches
2010-01-13 15:13                 ` Stefan Richter
2010-01-13 16:15                   ` Joe Perches
2010-01-13 17:10                     ` Stefan Richter
2010-01-15 20:03                       ` Pavel Machek
2010-01-06  1:20 ` [PATCH 6/8] net/netfilter/ipvs/ip_vs_ftp.c: Use standardized format in sprintf Joe Perches
2010-01-06  2:34   ` Simon Horman
2010-01-11 10:54     ` Patrick McHardy
2010-01-06  1:20 ` [PATCH 7/8] fs/ocfs2/cluster/tcp.c: Remove use of NIPQUAD, use %pI4 Joe Perches
2010-01-07  1:51   ` Joel Becker
2010-01-06  1:20 ` [PATCH 8/8] drivers/firmware/iscsi_ibft.c: Remove NIPQUAD_FMT, " Joe Perches

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=4B4B0806.40801@trash.net \
    --to=kaber@trash.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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