2008/5/29 Vegard Nossum <vegard.nossum@gmail.com>:<snip> The script is nice, but I'd wish it looked at a few other things as well. When I personally need to determine who to send patches to I do use 'git blame' for some of the addresses, but in addition to that I also check; - The comments at the top of the file. Sometimes there are email addresses there for relevant people (sometimes just names, but addresses can then usually be found for those people in CREDITS or MAINTAINERS). - Entries in MAINTAINERS that are relevant to the subsystem and/or file I'm modifying. - Entries in CREDITS that look relevant to the subsystem and/or file I'm modifying. - Names/email addresses in files in Documentation/ that are relevant to the subsystem/file I'm modifying. If the script could be made to check all (or just some) of those sources as well it would be really great. -- Jesper Juhl <jesper.juhl@gmail.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html --
| Andrew Morton | 2.6.23-rc3-mm1 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Yinghai Lu | Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption |
| Frederik Deweerdt | [-mm patch] remove tcp header from tcp_v4_check (take #2) |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Herbert Xu | Re: [PATCH 2/3][NET_BATCH] net core use batching |
git: | |
