On Mon, 2 May 2005, Judith Lebzelter wrote: > > > > > For the 'patch-2.6.12-rc3' results look at: > > > http://www.osdl.org/plm-cgi/plm?module=patch_info&patch_id=4381 > > > You can get to there by clicking on the name 'patch-2.6.12-rc3' under the > > > 'Applies Tree' Heading on the original results page. > > > > > > I believe that Bryce is planning on coming out with a more polished > > > difference report for this. > > > > This has a limited amount of utility, mostly because it can't tell us > > what errors were caused by the patch. It would be great to see if the > > applied patch makes any things fail that didn't fail before the patch. > > I don't really care if my patch breaks in some obscure module, if > > mainline breaks, too. > > > > I set this up mostly for Bryce, but thought others on the hotplug SIG > might be interested. He wanted this data for extracting the specific > additional errors or warnings between the 'mhp' patches and what they are > directly applied to (when there are any differences). This sounds like > what you would like to see? I think he has scripts which do intelligent > diffs on the *.err output files. That's right, and yeah I agree that manually parsing through the output is a pain (I used to do that!) But like Judith says, this is set up for me to get the data for my scripts. I'll watch the list for your new patch releases, then run my scripts to get the errors/warnings, and send a reply to the list with the boiled down errors and warnings. Easy! The detailed logs and info will be there if you ever feel like looking at more complete info, but in general you can ignore it as "behind the scenes" stuff. Oh, and while the patch pull and cross compile stuff is automated, my reports are not (yet). However, my goal is to get them posted within a couple hours of the patch coming out (barring meetings/vacation/fires/etc.) Bryce
