Comment 14 for bug 1157943

Could you guys please refrain from pinging me for comments without reading my previous comments?

Not only does this response now eat up all the time I have available for APT this week, its also highly demotivating to have the public record of two @canoncial.com people that they don't have to read bugreports if they can instead just ping volunteers like me to read for them.

The bugreport includes already all the information anyone needs to know to get an idea what I personally think about this "patch" (not that this would be important), the likelihood of https patches being accepted by me (APPROX ZERO BECAUSE I AM NOT DOING HTTPS STUFF) and what a real patch needs to use to fix the issue (hint CURLOPT_HEADERFUNCTION hint) and not just break it differently (e.g.: removing If-Range is not fixing anything, … ).

Anything else you two want me to comment? (Rhetoric question, answers would just be 'read' by my killfile, so don't do it)
Thanks!

David, who is really happy now he has opened his mailclient at 2 o'clock in the morning.