From: Joe Perches <joe@perches.com>
To: Paul Moore <paul.moore@hp.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: [NET]: Mark Paul Moore as maintainer of labelled networking.
Date: Tue, 28 Aug 2007 09:45:50 -0700 [thread overview]
Message-ID: <1188319550.6062.31.camel@localhost> (raw)
In-Reply-To: <20070828130813.E6A1D39C199@ldl.fc.hp.com>
On Tue, 2007-08-28 at 08:46 -0400, Paul Moore wrote:
> If having both a labeled networking and NetLabel maintainer entry is a
> problem then how about the patch below?
I don't think it is.
> -NETWORKING [LABELED] (NetLabel, CIPSO, Labeled IPsec, SECMARK)
> +NETWORKING [LABELED] (NetLabel/CIPSO, Labeled IPsec, SECMARK)
> P: Paul Moore
> M: paul.moore@hp.com
> +W: http://netlabel.sf.net (NetLabel/CIPSO)
> L: netdev@vger.kernel.org
> S: Maintained
My preference would be for something like:
NETLABEL and CIPSO
P: Paul Moore
M: paul.moore@hp.com
W: http://netlabel.sf.net
L: netdev@vger.kernel.org
S: Maintained
F: Documentation/netlabel/
F: include/net/netlabel.h
F: net/netlabel/
Labeled IPsec and SECMARK
P: Paul Moore
M: paul.moore@hp.com
L: netdev@vger.kernel.org
S: Supported
F: include/linux/netfilter/*SECMARK*
F: net/netfilter/*SECMARK*
I would like to add appropriate file patterns for each
block. Also, I'm not sure of the Supported/Maintained
status of each block.
The distinction is supposed to be:
Supported: Someone is actually paid to look after this.
Maintained: Someone actually looks after it.
Could you please clarify those for me?
cheers, Joe
next prev parent reply other threads:[~2007-08-28 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200708280001.l7S01Cxt004543@hera.kernel.org>
2007-08-28 6:46 ` [NET]: Mark Paul Moore as maintainer of labelled networking Joe Perches
2007-08-28 12:46 ` Paul Moore
2007-08-28 16:45 ` Joe Perches [this message]
2007-08-28 18:48 ` Paul Moore
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=1188319550.6062.31.camel@localhost \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
/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