From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp):
Date: Tue, 14 Aug 2007 11:42:36 -0700 [thread overview]
Message-ID: <1187116957.32555.136.camel@localhost> (raw)
In-Reply-To: <alpine.LFD.0.999.0708141112110.30176@woody.linux-foundation.org>
On Tue, 2007-08-14 at 11:15 -0700, Linus Torvalds wrote:
> Quite frankly, I think the MAINTAINERS file gets a whole lot uglier this
> way.
Me too.
Chopping up the current file is simple.
How about keeping the whole thing in git?
Please look at thread:
[PATCH] [1/2many] - Find the maintainer(s) for a patch - scripts/get_maintainer.pl
> In other words, it would be much better to just have per-file markers,
> along with some per-subdirectory stuff or similar.
Perhaps a single top-level MAINTAINERS subdirectory with
500+ files or MAINTAINERS per subdirectory.
Doesn't matter to me.
I'd prefer no per-file external markers,
nor embedded per-file keywords.
next prev parent reply other threads:[~2007-08-14 18:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:36 [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp): joe
2007-08-13 14:18 ` Pavel Machek
2007-08-13 20:50 ` Rafael J. Wysocki
2007-08-13 20:54 ` Joe Perches
2007-08-13 21:25 ` Rafael J. Wysocki
2007-08-13 21:21 ` Joe Perches
2007-08-13 21:38 ` Rafael J. Wysocki
2007-08-14 7:05 ` Pavel Machek
2007-08-14 17:37 ` Rafael J. Wysocki
2007-08-14 17:57 ` Joe Perches
2007-08-14 18:14 ` Rafael J. Wysocki
2007-08-14 18:15 ` Linus Torvalds
2007-08-14 18:22 ` Andrew Morton
2007-08-14 23:24 ` Dave Jones
2007-08-15 2:51 ` Kyle Moffett
2007-08-15 11:21 ` Rafael J. Wysocki
2007-08-16 13:04 ` Storing Maintainers info around the kernel tree Kyle Moffett
2007-08-16 15:13 ` Rene Herman
2007-08-16 15:31 ` [linux-pm] " Alan Stern
2007-08-16 15:50 ` Rene Herman
2007-08-16 21:39 ` Stefan Richter
2007-08-17 1:43 ` Rene Herman
2007-08-17 1:58 ` Alan Stern
2007-08-17 2:18 ` Rene Herman
2007-08-17 6:25 ` Stefan Richter
2007-08-14 18:25 ` [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp): Rene Herman
2007-08-14 18:42 ` Joe Perches [this message]
2007-08-15 1:45 ` 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=1187116957.32555.136.camel@localhost \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--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