On Sat, 02 Jun 2012 20:32:36 -0400
James Cloos wrote:
> What's up with md5-cache?
>
> Every syn has to pull the entire md5-cache hierarchy over again, as if
> some daemon re-creates every file every day, rather than only
> re-writing those files which need updates and adding/removing those
> whi
On 06/02/2012 08:52 PM, James Cloos wrote:
>> "ZM" == Zac Medico writes:
>
> Thanks for the quick reply and the reference to the bz.
>
> ZM> We had a bug about that [1] when we first deployed md5-cache, but it's
> ZM> supposed to have been fixed.
>
> It is not fixed. The behavior has not c
> "ZM" == Zac Medico writes:
Thanks for the quick reply and the reference to the bz.
ZM> We had a bug about that [1] when we first deployed md5-cache, but it's
ZM> supposed to have been fixed.
It is not fixed. The behavior has not changed in any way since md5-cache was
added.
ZM> [1] htt
On 06/02/2012 05:32 PM, James Cloos wrote:
> What's up with md5-cache?
>
> Every syn has to pull the entire md5-cache hierarchy over again, as if
> some daemon re-creates every file every day, rather than only re-writing
> those files which need updates and adding/removing those which need that.
What's up with md5-cache?
Every syn has to pull the entire md5-cache hierarchy over again, as if
some daemon re-creates every file every day, rather than only re-writing
those files which need updates and adding/removing those which need that.
Even if only the files metatdata changes, that still
