Thread (9 messages) 9 messages, 4 authors, 2007-08-17

Re: Re: Storing Maintainers info around the kernel tree

From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Date: 2007-08-17 06:31:21
Also in: linux-pm, lkml

Rene Herman wrote:
On 08/17/2007 03:58 AM, Alan Stern wrote:
quoted
On Fri, 17 Aug 2007, Rene Herman wrote:
quoted
On 08/16/2007 11:39 PM, Stefan Richter wrote:
quoted
Rene Herman wrote:
quoted
quoted
quoted
quoted
I personally don't think there's a whole lot wrong with more and
more expecting people who submit patches (for whom this automation
is intended) to be using git.
You mean "people who frequently submit patches for various different
subsystems".
Erm, I guess. Is that agreeing or disagreeing with me?
Don't forget also that the MAINTAINERS information is (or should be!)
used by people who want to submit bug reports, not just by people who
submit patches.  Bug reporters shouldn't need to use Git.
Yes, problem reporters and people who infrequently (or for their first
time) submit patches, and even people who frequently submit patches but
most of the time only to the same one or two subsystems need an obvious,
tool-independent way to get contact information.
Like I said:
quoted
quoted
If it's about non-developer users, I suspect it would to a fairly large
degree be an "in theory" thing to expect that said user does want the
information in a downloaded releases, but not in git, and not online
where git-web could also easily display all the information right
alongside the files.
And again, generating the MAINTAINERS file/info into releases is fine as
well.
Good.  This generated data will be used by almost everyone except for a
certain special group of submitters.
-- 
Stefan Richter
-=====-=-=== =--- =---=
http://arcgraph.de/sr/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help