I'll stop spamming the lists with this message now - Evolution just stopped trying to send it (7 times it seems) and so I couldn't tell it had already gone.
Time to get a better mail client. Sigh, still weekend soon. ----- Original Message ----- From: "Andrew Stitcher" <[email protected]> To: [email protected], "qpid developers" <[email protected]> Cc: [email protected] Sent: Friday, December 12, 2014 3:25:53 PM Subject: PROTON-772: New proton logging code Alan recently landed a change which stops the proton library from writing directly to stderr/stdout - this is a good thing (IMO). However I question a couple of things: 1. This change adds to the external API and so should have been reviewed (again IMO). reviews.apache.org now does work with the proton git repo. 2. I don't think this change should be an external API at all - at least not initially, perhaps with some user pressure. 3. There is already logging code triggered by PB_TRACE_FRM, PN_TRACE_RAW, PN_TRACE_DRV it would make sense for this to be integrated with the new work. Especially as this allows you to specify the tracer used (using pn_transport_set_tracer()). Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
