On Wed, 2007-11-28 at 00:56 +0000, Matt Nordhoff wrote:
> Robert Collins wrote:
> > I think we should keep this open a bit longer.
> >
> > Specifically, the current code assumes all files are equally hard to
> > cache. This is bogus.
> >
> > e.g.
> > foo.knit: not safe to cache
> > foo.kndx: not safe to cache
> > branch.conf: not safe to cache
> > 3847868641027641243.pack: safe to cache
> > 3847868641027641243.iix: safe to cache
> > branch-format: safe to cache
> > format: safe to cache
> > lock/*: not safe to cache.
> >
> > etc.
>
> branch-format and format aren't really safe to cache. What if someone
> runs 'bzr upgrade'?
On Wed, 2007-11-28 at 00:56 +0000, Matt Nordhoff wrote: 1243.pack: safe to cache 1243.iix: safe to cache
> Robert Collins wrote:
> > I think we should keep this open a bit longer.
> >
> > Specifically, the current code assumes all files are equally hard to
> > cache. This is bogus.
> >
> > e.g.
> > foo.knit: not safe to cache
> > foo.kndx: not safe to cache
> > branch.conf: not safe to cache
> > 384786864102764
> > 384786864102764
> > branch-format: safe to cache
> > format: safe to cache
> > lock/*: not safe to cache.
> >
> > etc.
>
> branch-format and format aren't really safe to cache. What if someone
> runs 'bzr upgrade'?
Well, there's safe and safe I guess.
on the one hand those files change very rarely.
on the other they matter quite a bit :).
-Rob www.robertcolli ns.net/ keys.txt>.
--
GPG key available at: <http://