Comment 4 for bug 316357

The associated branch contains a trivial implementation to catch SIGWINCH.

I tested it by running 'bzr selftest -s bt.test_http' and this reveals a fundamental flaw: catching the signal can interrupt an IO and if the code base is not ready to handle that, we can get weird failures.

I don't know if it's worth handling for a cosmetic benefit but people can play with it in a plugin if they really want and have valid use cases for that.