Skip to content
Snippets Groups Projects
  1. Aug 06, 2014
  2. Sep 16, 2013
  3. Jan 13, 2013
    • Kevin Bullock's avatar
      filtering: rename filters to their antonyms · f3b21beb
      Kevin Bullock authored
      Now that changelog filtering is in place, it's become evident that
      naming the filters according to the set of revs _not_ included in the
      filtered changelog is confusing. This is especially evident in the
      collaborative branch cache scheme.
      
      This changes the names of the filters to reflect the revs that _are_
      included:
      
        hidden -> visible
        unserved -> served
        mutable -> immutable
        impactable -> base
      
      repoview.filteredrevs is renamed to filterrevs, so that callers read a
      bit more sensibly, e.g.:
      
        filterrevs('visible') # filter revs according to what's visible
      f3b21beb
  4. Jan 02, 2013
    • Pierre-Yves David's avatar
      clfilter: add impactable filter · 58ca19ed
      Pierre-Yves David authored
      The `mutable` filter still have some chance to get invalidated. This will happen
      when:
      
      - you garbage collect hidden changeset,
      - public phase is moved backward,
      - something is changed in the filtering (this could be fixed)
      
      So we introduce an even more stable filtering set: everything with a revision
      number egal or higher than the first mutable changeset is filtered.
      
      The only official use of this filter is for branchcache.
      58ca19ed
    • Pierre-Yves David's avatar
      clfilter: add mutable filtering · aff706b3
      Pierre-Yves David authored
      It filters all mutable changesets, leaving only public changeset unfiltered.
      This filtering set is expected to be much more stable that the previous one as
      public changeset are unlikely to disapear.
      
      The only official use of this filter is for branchcache.
      aff706b3
  5. Jan 07, 2013
    • Pierre-Yves David's avatar
      branchmap: allow to use cache of subset · a55b0688
      Pierre-Yves David authored
      Filtered repository are *subset* of unfiltered repository. This means that a
      filtered branchmap could be use to compute the unfiltered version.
      
      And filtered version happen to be subset of each other:
      - "all() - unserved()" is a subset of "all() - hidden()"
      - "all() - hidden()" is a subset of "all()"
      
      This means that branchmap with "unfiltered" filter can be used as a base for
      "hidden" branchmap that itself could be used as a base for unfiltered
      branchmap.
      
         unserved < hidden < None
      
      This changeset implements this mechanism. If the on disk branchcache is not valid
      we use the branchcache of the nearest subset as base instead of computing it from
      scratch. Such fallback can be cascaded multiple time is necessary.
      
      Note that both "hidden" and "unserved" set are a bit volatile. We will add more
      stable filtering in next changesets.
      
      This changeset enables collaboration between no filtering and "unserved"
      filtering. Fixing performance regression introduced by 47f00b0de337
      a55b0688
  6. Jun 10, 2012
  7. Mar 01, 2012
    • Javi Merino's avatar
      tests: ignore the return code of chmod in test-inherit-mode · 7cf8de5a
      Javi Merino authored
      In freebsd, a newly created directory has the same group as the parent
      directory by default.  That means that the test directory created by
      test-inherit-mode.t is owned by root's group, so "chmod g+s .hg/store"
      fails to set the SGID bit and returns 1.  If we ignore chmod's return
      code, the testsuite passes again.
      7cf8de5a
  8. Jan 30, 2012
  9. Jan 13, 2012
  10. Nov 10, 2011
  11. Nov 07, 2011
  12. May 01, 2011
    • Alexander Solovyov's avatar
      fix bookmarks rollback behavior · 89e7d35e
      Alexander Solovyov authored
      Before this patch undo.bookmarks was created on bookmarks write and
      not with other transaction-related files. There were two issues: first
      is that if you have changed bookmarks few times after a transaction
      happened, rollback will give you a state which can point to
      non-existing revision. Second is that if you have not changed
      bookmarks after a transaction, rollback will touch your state anyway.
      
      This change also adds `localrepo._writejournal` method, which can be
      used by other extensions to save their transaction-related backup in
      right time.
      89e7d35e
  13. Jan 04, 2011
    • jfh's avatar
      move tags.cache and branchheads.cache to a collected cache folder .hg/cache/ · 5ccdca7d
      jfh authored
      The generation of cache files like tags.cache and branchheads.cache is not an
      actual reflection of things changing in the whole of the .hg directory (like eg
      a commit or a rebase or something) but instead these cache files are just part
      of bookkeeping. As such its convienant to allow various clients to ignore file
      events to do with these cache files which would otherwise cause a double
      refresh. Eg one refresh might occur after a commit, but the act of refreshing
      after the commit would cause Mercurial to generate a new branchheads.cache which
      would then cause a second refresh, for clients.
      
      However if these cache files are moved into a directory like eg .hg/cache/ then
      GUI clients on OSX (and possibly other platforms) can happily ignore file events
      in this cache directory.
      5ccdca7d
  14. Oct 16, 2010
  15. Aug 30, 2010
  16. Mar 18, 2008
  17. Feb 21, 2008
  18. Feb 15, 2008
  19. Feb 10, 2008
  20. Feb 09, 2008
Loading