| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFA
|
To: |
Chris Wright <chrisw@xxxxxxxxxxxx> |
|
Subject: |
[Xen-devel] Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE |
|
From: |
Adrian Bunk <bunk@xxxxxxxxxx> |
|
Date: |
Mon, 13 Aug 2007 22:21:58 +0200 |
|
Cc: |
Randy Dunlap <randy.dunlap@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, virtualization@xxxxxxxxxxxxxx, joe@xxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx |
|
Delivery-date: |
Fri, 17 Aug 2007 09:57:25 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20070813191938.GI3672@xxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<46bffcb5.o/KKCq3EZH4S47k3%joe@xxxxxxxxxxx> <20070813185536.GH3672@xxxxxxxxxxxxxxxxxxxx> <20070813121005.af159d1d.randy.dunlap@xxxxxxxxxx> <20070813191938.GI3672@xxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mutt/1.5.16 (2007-06-11) |
On Mon, Aug 13, 2007 at 12:19:38PM -0700, Chris Wright wrote:
> * Randy Dunlap (randy.dunlap@xxxxxxxxxx) wrote:
> > On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> > > * joe@xxxxxxxxxxx (joe@xxxxxxxxxxx) wrote:
> > > > +F: arch/i386/xen/
> > > > +F: drivers/*/xen-*front.c
> > > > +F: drivers/xen/
> > > > +F: include/asm-i386/xen/
> > > > +F: include/xen/
> > >
> > > I think this data will easily become stale. What is the point again?
> >
> > Agreed. But not everyone wants to or should have to use git,
> > so what are the alternatives?
>
> Between git (or gitweb), existing MAINTAINERS and a bit of common
> sense (or extra sleuthing), I never perceived a significant problem.
For active kernel developers like you and me it's not a problem.
But for other people it's non-trivial to always figure out who the
maintainer of some part of the kernel is.
> Alternative could be to place info directly in source files. If not
> all of MAINTAINERS info, it could be a tag to reference the relevant
> MAINTAINERS entry.
Having the information in MAINTAINERS is what creates the least
redundancies.
> thanks,
> -chris
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home