Project:Test driven development infrastructure
Component:Code
Category:feature request
Priority:normal
Assigned:Unassigned
Status:active

Issue Summary

" I tmight make sense to present the actual output of the .rej files that patch produces in such cases."

Sounds like a good idea to me :)

Robin

Comments

#1

talked to webchick about idea...

She came up with store "rejected hunks" (heh) in a field and displaying on the testing results page.

This can be done, it has to be aggregated from testing slaves...so a bit of coding involved. This is really low on my priority list, but any else is welcome to make patch against PIFR (project_issue_file_review).