Hi, what's the procedure for moving a resolution of this issue forward?

The fix in #336 is quite small, and if the maintainers have some feedback, I'd be happy to incorporate it. Notably, the author of #339 seems to have encountered precisely this issue in Dropwizard.

Thanks,

Mark

---------- Forwarded message ---------
From: Mark Elliot <mark.elliot@gmail.com>
Date: Fri, Oct 7, 2016 at 4:37 AM
Subject: LOGBACK-1189: detect previous copyAttributeMap calls
To: <logback-user@qos.ch>

Hi, there's a serious functionality bug with logback-access described in LOGBACK-1189 (which also proposes a fix). I pushed a fix here https://github.com/qos-ch/logback/pull/336, and wonder when we might be able to get this merged and released.

I suspect http://mailman.qos.ch/pipermail/logback-user/2016-September/004800.html is another (and high profile) manifestation of this problem.

Thanks,

Mark