Hi folks,
I'd like to hack up some scripts that automatically scan and report findings on a daily basis, eg. on the linux-next tree. Obviously, nobody can seriously read this all at once, especially not on a daily basis. Therefore I need to: * split the findings (eg. by ruleset or affected files / subsystems) * filter out findings that already have been reported. The second part seems to be trickiest one, as the code might slightly change in the meantime, laeding to different patch outputs. Ignoring the @@ lines should at least drop a large portion of the duplicates, but I'll yet have to see how well that works ... Did anyone else already working on that topic ? --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering i...@metux.net -- +49-151-27565287 _______________________________________________ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci
