From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering
Date: Thu, 20 Jul 2017 15:50:02 -0700 [thread overview]
Message-ID: <1500591002.14415.17.camel@perches.com> (raw)
In-Reply-To: <CA+55aFwR+Y+hd8PcGJ+EFsROEekeAiiZ2co5q7-cRwpuVMWSyw@mail.gmail.com>
On Thu, 2017-07-20 at 11:03 -0700, Linus Torvalds wrote:
> On Thu, Jul 20, 2017 at 9:48 AM, Joe Perches <joe@perches.com> wrote:
> >
> > Same general concept, but then an expectation would be
> > relative paths for filename patterns.
>
> No, I actually think we really should require the filename patterns to
> be absolute, even if the MAINTAINERS file might be deep in the
> hierarchy.
So do I but I bet dollars to doughnuts it happens
because expectations are what people assume so use too.
> So file patterns absolutely would need to remain relative to the top
> of the repository, not to the location of the MAINTAINERS file.
yup.
next prev parent reply other threads:[~2017-07-20 22:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 21:40 [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering Randy Dunlap
2017-07-19 21:44 ` Andrew Morton
2017-07-20 0:08 ` Linus Torvalds
2017-07-20 0:18 ` Randy Dunlap
2017-07-20 0:18 ` Linus Torvalds
2017-07-20 0:19 ` Randy Dunlap
2017-07-20 0:26 ` Linus Torvalds
2017-07-20 0:35 ` Linus Torvalds
2017-07-20 0:53 ` Linus Torvalds
2017-07-20 1:04 ` Randy Dunlap
2017-07-20 1:05 ` Joe Perches
2017-07-20 3:12 ` Joe Perches
2017-07-20 4:24 ` Linus Torvalds
2017-07-20 4:36 ` Theodore Ts'o
2017-07-20 4:53 ` Linus Torvalds
2017-07-20 4:43 ` Joe Perches
2017-07-20 4:57 ` Linus Torvalds
2017-07-20 10:54 ` Michael Ellerman
2017-07-20 16:48 ` Joe Perches
2017-07-20 18:03 ` Linus Torvalds
2017-07-20 22:50 ` Joe Perches [this message]
2017-07-19 21:49 ` 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=1500591002.14415.17.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--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 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.