From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Rene Herman <rene.herman@gmail.com>
Cc: Salikh Zakirov <salikh@gmail.com>,
LKML Kernel <linux-kernel@vger.kernel.org>,
Kyle Moffett <mrmacman_g4@mac.com>,
Junio C Hamano <gitster@pobox.com>, Joe Perches <joe@perches.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-pm@lists.linux-foundation.org, git@vger.kernel.org
Subject: Re: Re: Storing Maintainers info around the kernel tree
Date: Fri, 17 Aug 2007 08:25:20 +0200 [thread overview]
Message-ID: <46C53F50.9040107@s5r6.in-berlin.de> (raw)
In-Reply-To: <46C5057C.5010602@gmail.com>
Rene Herman wrote:
> On 08/17/2007 03:58 AM, Alan Stern wrote:
>
>> On Fri, 17 Aug 2007, Rene Herman wrote:
>>
>>> On 08/16/2007 11:39 PM, Stefan Richter wrote:
>>>> Rene Herman wrote:
>
>>>>> 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:
>
>>> 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/
next prev parent reply other threads:[~2007-08-17 6:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44L0.0708162156550.9927-100000@netrider.rowland.org>
2007-08-17 2:18 ` Re: Storing Maintainers info around the kernel tree Rene Herman
[not found] ` <46C5057C.5010602@gmail.com>
2007-08-17 6:25 ` Stefan Richter [this message]
[not found] <46C4FD57.3000101@gmail.com>
2007-08-17 1:58 ` Alan Stern
[not found] <Pine.LNX.4.44L0.0708161128540.3757-100000@iolanthe.rowland.org>
2007-08-16 15:50 ` Rene Herman
[not found] ` <46C47246.9020800@gmail.com>
2007-08-16 21:39 ` Stefan Richter
[not found] ` <46C4C40C.4050406@s5r6.in-berlin.de>
2007-08-17 1:43 ` Rene Herman
[not found] <46C469A5.8020003@gmail.com>
2007-08-16 15:31 ` Alan Stern
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=46C53F50.9040107@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mrmacman_g4@mac.com \
--cc=rene.herman@gmail.com \
--cc=salikh@gmail.com \
--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