From: Joe Perches <joe@perches.com>
To: Paul Mackerras <paulus@samba.org>
Cc: torvalds@linux-foundation.org, linux-ppp@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] [384/2many] MAINTAINERS - PPP PROTOCOL DRIVERS AND
Date: Tue, 14 Aug 2007 00:38:56 +0000 [thread overview]
Message-ID: <1187051936.10249.335.camel@localhost> (raw)
In-Reply-To: <18112.61275.563391.321131@cargo.ozlabs.ibm.com>
On Tue, 2007-08-14 at 09:55 +1000, Paul Mackerras wrote:
> It seems poor form to have to rename the file just because of a
> deficiency in the tools.
How about an
X: exclude file pattern
?
prev parent reply other threads:[~2007-08-14 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:34 [PATCH] [384/2many] MAINTAINERS - PPP PROTOCOL DRIVERS AND joe
2007-08-13 9:38 ` Paul Mackerras
2007-08-13 15:35 ` Joe Perches
2007-08-13 23:55 ` Paul Mackerras
2007-08-14 0:38 ` Joe Perches [this message]
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=1187051936.10249.335.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=paulus@samba.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).