Add file pattern to MAINTAINER entry
Signed-off-by: Joe Perches <[email protected]>
diff --git a/MAINTAINERS b/MAINTAINERS
index e4e1cc3..8395aba 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5153,6 +5153,11 @@ M: [email protected]
L: [email protected]
L: [email protected]
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
* [email protected] ([email protected]) wrote:
> Add file pattern to MAINTAINER entry
>
> Signed-off-by: Joe Perches <[email protected]>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e4e1cc3..8395aba 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5153,6 +5153,11 @@ M: [email protected]
> L: [email protected]
> L: [email protected]
> 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:
> * [email protected] ([email protected]) wrote:
> > Add file pattern to MAINTAINER entry
> >
> > Signed-off-by: Joe Perches <[email protected]>
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index e4e1cc3..8395aba 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -5153,6 +5153,11 @@ M: [email protected]
> > L: [email protected]
> > L: [email protected]
> > 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 ([email protected]) wrote:
> On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> > * [email protected] ([email protected]) 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
On Mon, 13 Aug 2007 12:10:05 PDT, Randy Dunlap said:
> Agreed. But not everyone wants to or should have to use git,
> so what are the alternatives?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree
and start chasing down 'History' pointers?
(Of course, mentioning that in Documentation/somewhere would be a good start)
On Mon, Aug 13, 2007 at 03:22:59PM -0400, [email protected] wrote:
> On Mon, 13 Aug 2007 12:10:05 PDT, Randy Dunlap said:
>
> > Agreed. But not everyone wants to or should have to use git,
> > so what are the alternatives?
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree
>
> and start chasing down 'History' pointers?
>...
And that brings you what?
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
On Mon, Aug 13, 2007 at 12:19:38PM -0700, Chris Wright wrote:
> * Randy Dunlap ([email protected]) wrote:
> > On Mon, 13 Aug 2007 11:55:36 -0700 Chris Wright wrote:
> > > * [email protected] ([email protected]) 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
On Mon, 13 Aug 2007 22:13:24 +0200, Adrian Bunk said:
> On Mon, Aug 13, 2007 at 03:22:59PM -0400, [email protected] wrote:
> > On Mon, 13 Aug 2007 12:10:05 PDT, Randy Dunlap said:
> >
> > > Agreed. But not everyone wants to or should have to use git,
> > > so what are the alternatives?
> >
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree
> >
> > and start chasing down 'History' pointers?
> >...
>
> And that brings you what?
You got a better alternative to 'git history' or 'git blame' to find who
to cc: regarding a bug, feel free to propose it. ;)
On Mon, Aug 13, 2007 at 04:32:19PM -0400, [email protected] wrote:
> On Mon, 13 Aug 2007 22:13:24 +0200, Adrian Bunk said:
> > On Mon, Aug 13, 2007 at 03:22:59PM -0400, [email protected] wrote:
> > > On Mon, 13 Aug 2007 12:10:05 PDT, Randy Dunlap said:
> > >
> > > > Agreed. But not everyone wants to or should have to use git,
> > > > so what are the alternatives?
> > >
> > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=tree
> > >
> > > and start chasing down 'History' pointers?
> > >...
> >
> > And that brings you what?
>
> You got a better alternative to 'git history' or 'git blame' to find who
> to cc: regarding a bug, feel free to propose it. ;)
Joe's patches
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
> 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 [email protected]?
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