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

On 8/12/07, Joe Perches <[email protected]> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
    • From: Adrian Bunk <[email protected]>
  • Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
    • From: [email protected]

• References:
  • [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
    • From: Joe Perches <[email protected]>

• Prev by Date: Re: [PATCH] Firmware class name collision
• Next by Date: Re: [PATCH] [385/2many] MAINTAINERS - PPP OVER ATM (RFC 2364)
• Previous by thread: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
• Next by thread: Re: [PATCH] [1/2many] - FInd the maintainer(s) for a patch - scripts/get_maintainer.pl
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]