WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

[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: 2007年8月13日 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: 2007年8月13日 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 2007年8月13日 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
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-devel] Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE , Chris Wright
Next by Date: [Xen-devel] Re: [XenPPC] [PATCH 1/4] xencomm take 2: xen side varisous fixes and preparation for consolidation , Hollis Blanchard
Previous by Thread: [Xen-devel] Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE , Randy Dunlap
Next by Thread: [Xen-devel] Re: [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE , Adrian Bunk
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /