Evolution Data Server Code Freeze Break



Requesting a code freeze break to address
http://bugzilla.gnome.org/show_bug.cgi?id=568332

A patch we added recently to mimic Firefox's fsync() workaround was
found to leak threads, causing Evolution to refuse to display messages
after running for a few hours.  I reworked the patch yesterday and came
up with a simpler design that doesn't leak.  Would like to commit this
prior to 2.26.0.

Several people at Red Hat are testing the patch and I hope to get
confirmation from them in the next day or so.  Seems to be working fine
for me so far.

Matthew Barnes

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]