-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/2011 02:59 PM, Sumit Bose wrote:
> On Thu, Feb 10, 2011 at 02:38:16PM -0500, Stephen Gallagher wrote:
> On 02/10/2011 07:07 AM, Sumit Bose wrote:
On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote:
There are several pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/10/2011 07:07 AM, Sumit Bose wrote:
> On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote:
> There are several problems with how we determine what entries to purge
> from the cache during the cleanup task in 1.2.x. Rather than expen
On Thu, Feb 10, 2011 at 02:38:16PM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/10/2011 07:07 AM, Sumit Bose wrote:
> > On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote:
> > There are several problems with how we determine what entrie
On Wed, Feb 09, 2011 at 12:21:00PM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> There are several problems with how we determine what entries to purge
> from the cache during the cleanup task in 1.2.x. Rather than expend the
> energy trying to track them do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are several problems with how we determine what entries to purge
from the cache during the cleanup task in 1.2.x. Rather than expend the
energy trying to track them down, it makes sense to disable the cleanup
task by default.
The only purpose of