From: Rene Herman <rene.herman@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>, "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 20:25:43 +0200 [thread overview]
Message-ID: <46C1F3A7.3090007@gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708141112110.30176@woody.linux-foundation.org>
On 08/14/2007 08:15 PM, Linus Torvalds wrote:
> Quite frankly, I think the MAINTAINERS file gets a whole lot uglier this
> way.
>
> There's also a rather fundamental issue: this will likely make people
> touch the MAINTAINERS file *more*, and from a maintenance standpoint, that
> is exactly the wrong thing to have (one central file that everybody
> touches). It just tends to generate unnecessary merge conflicts etc.
>
> (We used to have that issue with the central configuration file, for
> example).
>
> So the more I look at these things, the more convinced I am that this is
> not the right thing to do. These things should *not* be in one huge file,
> and I'd much much rather have the maintainership information be carried
> along with the subsystem itself, or the files it contains.
>
> In other words, it would be much better to just have per-file markers,
> along with some per-subdirectory stuff or similar.
Joe just now convinced me that rather than the per-file markers, the marker
is meta-information that could just be stored in GIT, with the MAINTAINERS
file turning into something generated.
git info --maintainer and such (for many possible kinds of --flags) would
throw out the information.
Rene.
next prev parent reply other threads:[~2007-08-14 18:30 UTC|newest]
Thread overview: 56+ 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 14:18 ` Pavel Machek
2007-08-13 20:50 ` Rafael J. Wysocki
2007-08-13 20:50 ` Rafael J. Wysocki
2007-08-13 20:54 ` Joe Perches
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:21 ` Joe Perches
2007-08-13 21:38 ` Rafael J. Wysocki
2007-08-13 21:38 ` Rafael J. Wysocki
2007-08-14 7:05 ` Pavel Machek
2007-08-14 7:05 ` Pavel Machek
2007-08-14 17:37 ` Rafael J. Wysocki
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:14 ` Rafael J. Wysocki
2007-08-14 18:15 ` Linus Torvalds
2007-08-14 18:15 ` Linus Torvalds
2007-08-14 18:22 ` Andrew Morton
2007-08-14 23:24 ` Dave Jones
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 ` Alan Stern
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-16 21:39 ` [linux-pm] " Stefan Richter
2007-08-17 1:43 ` Rene Herman
2007-08-17 1:43 ` [linux-pm] " Rene Herman
2007-08-17 1:58 ` Alan Stern
2007-08-17 2:18 ` Rene Herman
2007-08-17 2:18 ` [linux-pm] " Rene Herman
2007-08-17 6:25 ` Stefan Richter
2007-08-17 6:25 ` [linux-pm] " Stefan Richter
2007-08-17 1:58 ` Alan Stern
2007-08-16 15:50 ` Rene Herman
2007-08-16 15:13 ` Rene Herman
2007-08-16 13:04 ` Kyle Moffett
2007-08-15 11:21 ` [PATCH] [443/2many] MAINTAINERS - HIBERNATION (aka Software Suspend, aka swsusp): Rafael J. Wysocki
2007-08-15 2:51 ` Kyle Moffett
2007-08-14 18:22 ` Andrew Morton
2007-08-14 18:25 ` Rene Herman
2007-08-14 18:25 ` Rene Herman [this message]
2007-08-14 18:42 ` Joe Perches
2007-08-14 18:42 ` Joe Perches
2007-08-15 1:45 ` Joe Perches
2007-08-15 1:45 ` Joe Perches
2007-08-14 17:57 ` Joe Perches
2007-08-13 21:25 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2007-08-13 6:36 joe
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=46C1F3A7.3090007@gmail.com \
--to=rene.herman@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--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 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.