2008/5/29 Vegard Nossum <vegard.nossum@xxxxxxxxx>: > Hi, > > I've written this perl script that takes a patch as input and prints the > authors/committers of the affected lines, using git-blame as the back end. > > (The purpose of this is of course to find out whom to send patches to.) > <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@xxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
