On Thu, 2016-01-14 at 15:42 +0100, Ludwig Krispenz wrote:
> We had many issues with the retro changelog plugin. The main reason
> is
> that the retro CL is a separate backend and if there is more than
> one
> regular backend it is easy to run into deadlocks, eg a change in
> backend
> A
On 01/14/2016 09:42 AM, Ludwig Krispenz wrote:
We had many issues with the retro changelog plugin. The main reason is
that the retro CL is a separate backend and if there is more than one
regular backend it is easy to run into deadlocks, eg a change in
backend A triggers and ADD in theh RCL,
On 01/14/2016 04:08 PM, Mark Reynolds wrote:
On 01/14/2016 09:42 AM, Ludwig Krispenz wrote:
We had many issues with the retro changelog plugin. The main reason
is that the retro CL is a separate backend and if there is more than
one regular backend it is easy to run into deadlocks, eg a