Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch -scripts/get_maintainer.pl

[Adrian Bunk]

On Mon, Aug 13, 2007 at 10:09:08AM -0700, Ray Lee wrote:
> On 8/12/07, Joe Perches <joe@xxxxxxxxxxx> wrote:
> > I grew weary of looking up the appropriate
> > maintainer email address(es) to CC: for a patch.
> >
> > I added flags to the MAINTAINERS file
> >
> > F:      file pattern
> >
> > for each maintained block and a script to parse
> > the modified blocks for maintainer and list
> > email addresses.
> 
> Why not parse git annotate or blame instead (other than it's freakin'
> slow)? Using the repository history has the added benefit of telling
> you a lot more fine-grained detail about who may want to know about
> your patch.

The git tree simply does not contain this information.

Some of the obvious problems:
- recently changed maintainership
- new maintainer email address with the old one bouncing
- git never contains maintainer mailing list addresses
- you can't distinguish between a maintainer of a driver and people only
  writing or forwarding patches for a driver

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/