[PATCH 3 of 8 filtering] clfilter: introduce an "unfiltered" method on localrepo

Idan Kamara idankk86 at gmail.com
Wed Nov 21 02:39:41 CST 2012


On Wed, Nov 21, 2012 at 2:11 AM, Pierre-Yves David
<pierre-yves.david at ens-lyon.org> wrote:
> # HG changeset patch
> # User Pierre-Yves David <pierre-yves.david at ens-lyon.org>
> # Date 1353454589 -3600
> # Node ID 4ae17fd97c2b3e0f9972c9cc093a3bc5e77c3f67
> # Parent  80f2f2c90a15af59fa9175b6520d7659acc7bb15
> clfilter: introduce an "unfiltered" method on localrepo
>
> This commit is part of the changelog level filtering effort. It returns the main
> "unfiltered" version of a repo-like object. For localrepo this mean the same
> localrepo object. But this method will be overwritten by filtered version of a
> repository to returns the core unfiltered version of the repo.
>
> Introducing this simple first allows later commit to prepare the landing of
> filtered version a repository.

We haven't seen this part yet but I'm curious if the filtered and unfiltered
repos will stay in-sync, e.g.:

  r = repo.unfiltered()
  r... # do something that causes rev X to become filtered/unfiltered
  repo[X] # what happens here?


More information about the Mercurial-devel mailing list