* John Goerzen <jgoer...@complete.org> [2009-07-06 08:10:45 -0500]: > Hey guys, > > Can you try reverting patch 2e22b4123190c8ae434efb2bfb3d507694482644 and > let me know if that fixes it? I'd like to isolate which commit caused > the problem, and revert it, rather than try to patch on top of it. > > Other patches that might be culprits could be: > > d69176090c4afb220df566ef5ed5e653933be45e > 817c09a4607f45635a6f327cebc593e396723514 > 3847d0ba9d17f42cbb4ae15ea9cfb97aca2029ca > e1fb9492f84538df698d6a2f1cfa2738929ed040 >
Reverting each one of the above patches (one by one) didn't solve the issue. After bisecting, the patch introducing the misbehavior is one of: 61567d0d3641bddab88911fc9e216c8f213525cf e1fb9492f84538df698d6a2f1cfa2738929ed040 147265ac391c9feeae88ddcac5b6685c87d4a39b Unfortunately I couldn't test the first two patches alone, because 61567d0d introduces the use of SigListener, which is defined in 147265ac. My patch modifies the SigListener introduced in the last commit referenced above. How would you like to proceed? Thanks for your work! -- Nicolas Dandrimont BOFH excuse #128: Power Company having EMP problems with their reactor
signature.asc
Description: Digital signature
