atom feed19 messages in com.selenic.mercurial-devel[PATCH 00 of 11] filecache decorator
FromSent OnAttachments
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Idan KamaraJul 16, 2011 7:34 am 
Adrian BuehlmannJul 16, 2011 9:03 am 
Matt MackallJul 18, 2011 1:12 pm 
Adrian BuehlmannJul 18, 2011 1:32 pm 
Matt MackallJul 18, 2011 2:29 pm 
Adrian BuehlmannJul 18, 2011 3:26 pm 
Idan KamaraJul 19, 2011 3:23 am 
Adrian BuehlmannJul 19, 2011 4:53 am 
Subject:[PATCH 00 of 11] filecache decorator
From:Idan Kamara (idan@gmail.com)
Date:Jul 16, 2011 7:34:31 am
List:com.selenic.mercurial-devel

This series introduces a filecache decorator that can be used on localrepo functions, replacing propertycache.

The general idea is being able to associate a file with a property, and watch that file stat info for modifications when we decide it's important for it to be up-to-date. Once it changes, we recreate the object.

As a consequence, localrepo.invalidate() will become much less expensive in the case where nothing changed on-disk (branchcache being the exception here, I haven't dealt with that yet).

The end goal of this series is to allow the command server's cached repository to stay in-sync with changes happening to the repository on the outside.