From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
Joe Perches <joe@perches.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
Date: Mon, 13 Aug 2007 16:37:25 -0400 [thread overview]
Message-ID: <1187037445.6628.98.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1187026955.2688.4.camel@laptopd505.fenrus.org>
On Mon, 2007-08-13 at 10:42 -0700, Arjan van de Ven wrote:
> The maintainer info should be in the source file itself! That's the only
> reasonable way to keep it updated; now I'm all for having it machine
> parsable so that tools can use it, but it still really should be in the
> code itself, not in some central file that will always just go out of
> data, and will be a huge source of needless patch conflicts.
If the problem is to do with people failing to update the MAINTAINERS
file, why would moving the same data into 20 or 30 source files motivate
them to keep it up to date? As far as I can see, that would just serve
to multiply the amount of stale data...
Trond
next prev parent reply other threads:[~2007-08-13 20:38 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 5:49 Joe Perches
2007-08-13 6:42 ` Michal Piotrowski
2007-08-13 7:16 ` Al Viro
2007-08-13 16:22 ` Sam Ravnborg
2007-08-13 17:40 ` Rene Herman
2007-08-13 15:43 ` Kok, Auke
2007-08-13 19:40 ` Richard Knutsson
2007-08-13 20:28 ` Kok, Auke
2007-08-13 20:43 ` Richard Knutsson
2007-08-13 17:09 ` Ray Lee
2007-08-13 18:11 ` Valdis.Kletnieks
2007-08-13 21:04 ` Adrian Bunk
2007-08-13 17:33 ` Mariusz Kozlowski
2007-08-13 17:42 ` Arjan van de Ven
2007-08-13 18:07 ` Mariusz Kozlowski
2007-08-13 18:10 ` Rene Herman
2007-08-13 18:32 ` Satyam Sharma
2007-08-13 19:21 ` Jan Engelhardt
2007-08-13 19:53 ` Richard Knutsson
2007-08-13 20:05 ` Valdis.Kletnieks
2007-08-13 18:41 ` Krzysztof Halasa
2007-08-13 19:02 ` Krzysztof Halasa
2007-08-13 20:16 ` Theodore Tso
2007-08-13 20:37 ` Trond Myklebust [this message]
2007-08-14 1:19 ` Arjan van de Ven
2007-08-14 1:48 ` John W. Linville
2007-08-14 1:51 ` Rene Herman
2007-08-14 2:04 ` Rene Herman
2007-08-14 9:20 ` Alan Cox
2007-08-14 13:47 ` Arjan van de Ven
2007-08-14 14:28 ` Adrian Bunk
2007-08-14 14:33 ` Arjan van de Ven
2007-08-14 15:53 ` Rene Herman
2007-08-14 17:00 ` Joe Perches
2007-08-14 18:03 ` Rene Herman
2007-08-14 18:28 ` Joe Perches
2007-08-14 18:33 ` Rene Herman
2007-08-14 18:40 ` Linus Torvalds
2007-08-14 18:54 ` Joe Perches
2007-08-14 19:33 ` Al Viro
2007-08-14 19:57 ` Joe Perches
2007-08-15 1:19 ` Rene Herman
2007-08-15 13:33 ` Satyam Sharma
2007-08-15 13:39 ` Rene Herman
2007-08-15 13:52 ` Kyle Moffett
2007-08-16 10:58 ` Rene Herman
2007-08-16 11:08 ` Rene Herman
2007-08-16 11:26 ` Salikh Zakirov
2007-08-16 11:57 ` Rene Herman
2007-08-16 15:40 ` Al Viro
2007-08-16 15:53 ` Rene Herman
2007-08-16 19:00 ` Junio C Hamano
2007-08-17 4:24 ` Rene Herman
2007-08-15 19:37 ` Krzysztof Halasa
2007-08-15 23:19 ` Al Viro
2007-08-15 1:35 ` Richard Knutsson
2007-08-15 9:29 ` Stefan Richter
2007-08-15 15:31 ` Ray Lee
2007-08-16 20:36 ` Joe Perches
2007-08-15 1:31 ` Junio C Hamano
2007-08-15 2:12 ` Joe Perches
2007-08-15 5:25 ` Junio C Hamano
2007-08-15 5:42 ` Rene Herman
2007-08-15 9:39 ` Stefan Richter
2007-08-15 11:44 ` Rene Herman
2007-08-15 17:26 ` Joe Perches
2007-08-17 2:13 ` Joe Perches
2007-08-17 2:30 ` Joe Perches
2007-08-17 17:54 ` [PATCH] - git-send-email.perl Joe Perches
2007-08-17 23:38 ` Junio C Hamano
2007-08-18 1:51 ` Joe Perches
2007-08-14 14:22 ` [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl Adrian Bunk
2007-08-14 14:33 ` Arjan van de Ven
2007-08-14 14:45 ` John W. Linville
2007-08-14 2:15 ` Manu Abraham
2007-08-13 6:09 Joe Perches
2007-08-13 16:24 ` Sam Ravnborg
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=1187037445.6628.98.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.kozlowski@tuxland.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
all inboxes | Powered by JetHome®