Linux Virtualization - Aug 2007 - [PATCH] [545/2many] MAINTAINERS - XEN HYPERVISOR INTERFACE

Add file pattern to MAINTAINER entry

Signed-off-by: Joe Perches <joe@perches.com>

diff --git a/MAINTAINERS b/MAINTAINERS
index e4e1cc3..8395aba 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5153,6 +5153,11 @@ M:	chrisw@sous-sol.org
 L:	virtualization@lists.osdl.org
 L:	xen-devel@lists.xensource.com
 S:	Supported
+F:	arch/i386/xen/
+F:	drivers/*/xen-*front.c
+F:	drivers/xen/
+F:	include/asm-i386/xen/
+F:	include/xen/
 
 XFS FILESYSTEM
 P:	Silicon Graphics Inc

* joe@perches.com (joe@perches.com) wrote:
> Add file pattern to MAINTAINER entry
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e4e1cc3..8395aba 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5153,6 +5153,11 @@ M:	chrisw@sous-sol.org
>  L:	virtualization@lists.osdl.org
>  L:	xen-devel@lists.xensource.com
>  S:	Supported
> +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?

On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> * joe@perches.com (joe@perches.com) wrote:
> > Add file pattern to MAINTAINER entry
> > 
> > Signed-off-by: Joe Perches <joe@perches.com>
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index e4e1cc3..8395aba 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -5153,6 +5153,11 @@ M:	chrisw@sous-sol.org
> >  L:	virtualization@lists.osdl.org
> >  L:	xen-devel@lists.xensource.com
> >  S:	Supported
> > +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?


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

On Mon, 2007-08-13 at 11:55 -0700, Chris Wright wrote:
> I think this data will easily become stale.  What is the point again?
Write a patch, notify the appropriate maintainers.

* Randy Dunlap (randy.dunlap@oracle.com) wrote:
> On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> > * joe@perches.com (joe@perches.com) 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

> Agreed.  But not everyone wants to or should have to use git,
> so what are the alternatives?
Export the recent git history each release into an XML file at known
locations on the kernel web site. Wait for tools to appear

On Mon, Aug 13, 2007 at 09:54:50PM +0100, Alan Cox
wrote:
> > Agreed.  But not everyone wants to or should have to use git,
> > so what are the alternatives?
> 
> Export the recent git history each release into an XML file at known
> locations on the kernel web site. Wait for tools to appear
How can the git history tell me to send a Cc to netdev@vger.kernel.org?

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