From: Joe Perches <joe@perches.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@linux-foundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] [70/2many] MAINTAINERS - ARPD SUPPORT
Date: Mon, 13 Aug 2007 10:04:19 -0700 [thread overview]
Message-ID: <1187024659.10249.125.camel@localhost> (raw)
In-Reply-To: <20070813173522.685dab9e@the-village.bc.nu>
On Mon, 2007-08-13 at 17:35 +0100, Alan Cox wrote:
> I wouldn't add a pattern for this.
Back to:ARPD SUPPORT
P: Jonathan Layes
L: netdev@vger.kernel.org
S: Maintained
> Actually I think the entire thing is a
> bad idea but thats another matter.
Of course it's not an end-all solution,
but what might work better?
next prev parent reply other threads:[~2007-08-13 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:23 [PATCH] [70/2many] MAINTAINERS - ARPD SUPPORT joe
2007-08-13 10:49 ` Alan Cox
2007-08-13 15:46 ` Joe Perches
2007-08-13 16:35 ` Alan Cox
2007-08-13 17:04 ` Joe Perches [this message]
2007-08-13 17:51 ` Alan Cox
2007-08-15 8:10 ` Stefan Richter
2007-08-15 8:33 ` Alan Cox
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=1187024659.10249.125.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).