From: Pavel Machek <pavel@ucw.cz>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Joe Perches <joe@perches.com>,
Jan Engelhardt <jengelh@medozas.de>,
Patrick McHardy <kaber@trash.net>,
linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH V3] MAINTAINERS: Document list types, add "A:" section type, update NETFILTER
Date: Fri, 15 Jan 2010 21:03:43 +0100 [thread overview]
Message-ID: <20100115200343.GH1345@ucw.cz> (raw)
In-Reply-To: <4B4DFE84.2080304@s5r6.in-berlin.de>
On Wed 2010-01-13 18:10:28, Stefan Richter wrote:
> Joe Perches wrote:
> > On Wed, 2010-01-13 at 16:13 +0100, Stefan Richter wrote:
> >> Joe Perches wrote:
> >> > + A: Additional useful unstructured information.
> >> Can be implemented with a level of indirection via the W: entries.
> >
> > Mailing lists aren't web addresses.
>
> Project web sites typically contain contact pages (which is what you
> used the first two proposed A: entries for --- contacts that apparently
> do not play a role for patch submission), and web sites can carry any
> other "unstructured information".
>
> Keep redundancy low.
Well, I'd say that kernel maintainance info should be
kept... well... in kernel...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-01-15 20:03 UTC|newest]
Thread overview: 29+ 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 ` Joe Perches
2010-01-06 1:20 ` [Ocfs2-devel] " 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 ` 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
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 [this message]
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 ` [Ocfs2-devel] [PATCH 7/8] fs/ocfs2/cluster/tcp.c: Remove use of NIPQUAD, use %pI4 Joe Perches
2010-01-06 1:20 ` Joe Perches
2010-01-07 1:51 ` [Ocfs2-devel] " Joel Becker
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=20100115200343.GH1345@ucw.cz \
--to=pavel@ucw.cz \
--cc=jengelh@medozas.de \
--cc=joe@perches.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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.