On Wed, 8 Apr 2009, Jack Stone wrote: > Ingo Molnar wrote: > > * Jack Stone <jwjstone@xxxxxxxxxxx> wrote: > > > > > >> Ingo Molnar wrote: > >> > >>> No, i mean, this approach should be changed, and i dont think any > >>> type cast change should go via any trivial tree. It's easy to mess > >>> it up. Please submit them to the maintainer trees > >>> > >> Ok. I'll try and find appropriate CCs. I'm going out shortly so it > >> might take me a while. > >> > > > > Since you do many such patches it might make sense to script up a > > "who maintains what" kind of script - and share that script with > > lkml. > > > > I have this silly little script: > > > > git log $@ | grep Signed-off-by: | > > cut -d: -f2 | cut -d\< -f1 | > > sort | uniq -c | sort -n > > > > To find out any recent parties that touches a particular file. But > > it would be nice to somehow automate the pickup of mailing-list > > addresses from MAINTAINERS for example. We've literally got hundreds > > of email lists there. > > > > It is not trivial to do though :-) > > > It would be useful. The main problem is working out what files belong to > what MAINTAINERS entries. > > I'll see what I can cook up. This can be helpful: http://lwn.net/Articles/284469/ It's a bit out of date, though, because git-blame seems to have disappeared as a command. julia -- To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
