[PATCH 4 of 9] branchmap: read and write key part related to filtered revision
Idan Kamara
idankk86 at gmail.com
Thu Dec 27 02:30:29 CST 2012
On Thu, Dec 27, 2012 at 1:53 AM, Pierre-Yves David <
pierre-yves.david at ens-lyon.org> wrote:
>
>
> On 26 déc. 2012, at 22:09, Idan Kamara wrote:
>
> > On Wed, Dec 26, 2012 at 10:33 PM, Pierre-Yves David
> > <pierre-yves.david at ens-lyon.org> wrote:
> > >
> > > # HG changeset patch
> > > # User Pierre-Yves David <pierre-yves.david at logilab.fr>
> > > # Date 1356187406 -3600
> > > # Node ID ed03a82360c2b90195a2d4dacca205e5a705a1f2
> > > # Parent 4b098d0339f9e8b1805c4f6ef1d8bcf59f5a6349
> > > branchmap: read and write key part related to filtered revision
> > >
> > > Now that we have a third part for the cache key we need to write and
> > > read
> > > it on
> > > disk. It is only written when there is filtered revision. This keep
> > > the
> > > format
> > > compatible with older version.
> >
> > What will happen when an older client tries to use a newly
> > written cache?
>
> That does not happen.
>
> older client only tries to read `.hg/cache/branchheads`. This file
> contains the branchmap cache without any filtering applied. Therefore
> nothing is filtered and only tipnode and tiprev is written to disk exactly
> as the older format.
>
> Cache for filtered version has they own file that older version won't try
> to read.
Reading this patch alone doesn't suggest that but I see
it's changed in the next couple of patches in this series.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20121227/3f6b06b1/attachment.html>
More information about the Mercurial-devel
mailing list