Skip to content
Snippets Groups Projects
  1. Jan 18, 2021
  2. Jan 15, 2021
  3. Jan 18, 2021
    • Pulkit Goyal's avatar
      share: rework config options to be much clearer and easier · 25be21ec
      Pulkit Goyal authored
      Recently I implemented various boolean configs which control how to behave when
      there is a share-safe mismatch between source and share repository. Mismatch
      means that source supports share-safe where as share does not or vice versa.
      
      However, while discussion and documentation we realized that it's too
      complicated and there are some combinations of values which makes no sense.
      
      We decided to introduce a config option with 4 possible values which
      makes controlling and understanding things easier.
      
      The config option `share.safe-mismatch.source-{not-}safe` can have
      following 4 values:
      
      * abort (default): error out if there is mismatch
      * allow: allow to work with respecting share source configuration
      * {up|down}grade-abort: try to {up|down}grade, if it fails, abort
      * {up|down}grade-allow: try to {up|down}grade, if it fails, continue in allow
      mode
      
      
      I am not sure if I can explain 3 config options which I deleted right now in
      just 5 lines which is a sign of how complex they became.
      
      No test changes demonstrate that functionality is same, only names have changed.
      
      Differential Revision: https://phab.mercurial-scm.org/D9785
      25be21ec
  4. Jan 14, 2021
  5. Jan 18, 2021
  6. Jan 17, 2021
  7. Jan 16, 2021
  8. Jan 15, 2021
    • Pierre-Yves David's avatar
      clone: make sure we warm the cache after a clone · 95a615dd
      Pierre-Yves David authored
      This work around any deviciency/limitation of the clone process. In our case
      this ensure the persistent nodemap exist with valid content.
      
      Ideally, the cloning process would also do "the right thing". However since
      older server will never be able to do "the right thing". The local workaround
      will be necessary anyway.
      
      I am not worried by the performance impact of this as `hg clone` is non-instant
      on large repositories where is could matters. Warming the cache if they are
      already correct is very fast. And if they are not already warm, this seems like
      a good time to do so.
      
      This impact various test as more cache are now warmed sooner, all the change
      should be harmless.
      
      Differential Revision: https://phab.mercurial-scm.org/D9789
      95a615dd
  9. Jan 13, 2021
  10. Jan 15, 2021
  11. Jan 09, 2021
  12. Jan 11, 2021
  13. Jan 07, 2021
  14. Jan 09, 2021
  15. Jan 14, 2021
  16. Jan 15, 2021
  17. Jan 14, 2021
  18. Jan 13, 2021
  19. Dec 18, 2020
    • Jörg Sonnenberger's avatar
      branchmap: avoid ancestor computations in absence of non-continous branches · c4b792fa
      Jörg Sonnenberger authored
      The branchhead computation is one of the more heavy operations for
      bigger repositories as it has to scan all changesets and potentially
      involves the expensive computation of the ancestor sets. Redo the
      computation to handle the common cases directly and use tighter
      conditions for when the ancestor scan is necessary. Most importantly,
      avoid it completely if the non-continous branches are processed in one
      update as seen in the initial computation after a clone.
      
      For the Mercurial repository, it gives a small 2-3% performance boost.
      For the NetBSD test repository, it cuts the time in half.
      
      Differential Revision: https://phab.mercurial-scm.org/D9631
      c4b792fa
  20. Jan 12, 2021
  21. Jan 08, 2021
Loading