From: josh@joshtriplett.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Documentation: exceptions to what I maintain
Date: Thu, 12 Jun 2014 10:26:20 -0700 [thread overview]
Message-ID: <20140612172620.GA21930@cloud> (raw)
In-Reply-To: <5399DF99.2010701@infradead.org>
On Thu, Jun 12, 2014 at 10:12:57AM -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>
One comment below.
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- lnx-315-rc5.orig/MAINTAINERS
> +++ lnx-315-rc5/MAINTAINERS
> @@ -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)
Could we make this machine-readable, and teach scripts/get_maintainer.pl
to understand it? Two possible syntaxes:
F: Documentation/
F: !Documentation/ABI/
...
or:
F: Documentation/ (not Documentation/ABI ...)
next prev parent reply other threads:[~2014-06-12 17:26 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 [this message]
2014-06-12 17:35 ` Joe Perches
2014-06-12 17:49 ` Randy Dunlap
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=20140612172620.GA21930@cloud \
--to=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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