From: Randy Dunlap <rdunlap@infradead.org>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: [PATCH 2/2] Documentation: exceptions to what I maintain
Date: Thu, 12 Jun 2014 10:49:20 -0700 [thread overview]
Message-ID: <5399E820.5080801@infradead.org> (raw)
In-Reply-To: <1402594501.12385.10.camel@joe-AO725>
On 06/12/14 10:35, Joe Perches wrote:
> On Thu, 2014-06-12 at 10:12 -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Note that I don't maintain Documentation/ABI/,
>> Documentation/devicetree/, or the language translation files.
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>
> Hey Randy.
>
> Perhaps it's better to use exclusion "X:" values
> so get_maintainer doesn't still include you.
>
>> @@ -2885,7 +2885,7 @@ M: Randy Dunlap <rdunlap@infradead.org>
>> L: linux-doc@vger.kernel.org
>> T: quilt http://www.infradead.org/~rdunlap/Doc/patches/
>> S: Maintained
>> -F: Documentation/
>> +F: Documentation/ (but not: ABI, devicetree, translations)
>
> Maybe:
>
> X: Documentation/ABI/
> X: Documentation/devicetree/
> X: Documentation/[a-z][a-z]_[A-Z][A-Z]/
>
> The last line matches:
>
> Documentation/ja_JP/
> Documentation/ko_KR/
> Documentation/zh_CN/
>
> and it's easy to add any other directory you don't
> want to cc'd on.
Thanks, I'll modify it to that syntax.
That should satisfy Josh's comment also.
--
~Randy
next prev parent reply other threads:[~2014-06-12 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 17:12 [PATCH 2/2] Documentation: exceptions to what I maintain Randy Dunlap
2014-06-12 17:26 ` josh
2014-06-12 17:35 ` Joe Perches
2014-06-12 17:49 ` Randy Dunlap [this message]
2014-06-12 19:07 ` josh
2014-06-12 21:26 ` Randy Dunlap
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=5399E820.5080801@infradead.org \
--to=rdunlap@infradead.org \
--cc=joe@perches.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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