|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFA
To: |
Randy Dunlap <randy.dunlap@xxxxxxxxxx> |
Subject: |
[Xen-devel] Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE |
From: |
Chris Wright <chrisw@xxxxxxxxxxxx> |
Date: |
Mon, 13 Aug 2007 12:19:38 -0700 |
Cc: |
xen-devel@xxxxxxxxxxxxxxxxxxx, jeremy@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Chris Wright <chrisw@xxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxx, joe@xxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, torvalds@xxxxxxxxxxxxxxxxxxxx |
Delivery-date: |
Mon, 13 Aug 2007 12:21:17 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20070813121005.af159d1d.randy.dunlap@xxxxxxxxxx> |
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> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.5.14 (2007-02-12) |
* 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.
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.
thanks,
-chris
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|