Skip to content
Snippets Groups Projects
  1. Nov 10, 2021
  2. Nov 09, 2021
  3. Oct 26, 2021
    • Arseniy Alekseyev's avatar
      rhg: more efficient `HgPath::join` · 6d69e83e6b6e
      Arseniy Alekseyev authored
      This commit makes `HgPath::join` slightly more efficient
      by avoiding one copy.
      
      It also avoids a particularly inefficient (quadratic) use of
      `HgPath::join` by using a new mutating function `HgPathBuf::push` instead.
      
      The name for `HgPathBuf::push` is chosen by analogy to `PathBuf::push`.
      
      Differential Revision: https://phab.mercurial-scm.org/D11721
      6d69e83e6b6e
  4. Nov 09, 2021
  5. Oct 27, 2021
    • Arseniy Alekseyev's avatar
      rhg: make it possible to opt out of `rhg cat` · 698b70b9e8ea
      Arseniy Alekseyev authored
      The reason an opt-out is needed is that there are still behavior
      differences between `rhg cat` and `hg cat`:
      
      - it does not interpret relative paths correctly
      - it does not interpret patterns correctly, e.g. 're:foobar$' would be interpreted as a verbatim filename
      - it does not implement the correct semantics of relpath matcher: if given a directory, `hg` concatenates all files in this directory, while `rhg` simply complains
      
      Differential Revision: https://phab.mercurial-scm.org/D11723
      698b70b9e8ea
  6. Nov 09, 2021
    • Euxane TRAN-GIRARD's avatar
      tests: run the whole hg-core/path_auditor test in a clean temp dir · ab2dfc993b5c
      Euxane TRAN-GIRARD authored
      This makes the whole test happen in a clean temporary directory in
      `$TMPDIR/$random`, and simplifies the test a bit by eliminating unnecessarily
      dynamic path elements computations.
      
      Before this patch, the first part of the test was happening in `/tmp` itself.
      This allowed coincidentally named files placed in that directory to impact the
      outcome of the test. Additionally, this made the second part of the test fail
      on systems on which `$TMPDIR != /tmp`, because the inspected directory was
      different from the one in which the mock files were being written. This fully
      fixes the issue only partially solved in db2bc9e667a1.
      
      Differential Revision: https://phab.mercurial-scm.org/D11738
      ab2dfc993b5c
  7. Oct 20, 2021
  8. Oct 27, 2021
  9. Nov 04, 2021
  10. Nov 03, 2021
  11. Aug 25, 2021
  12. Oct 19, 2021
    • Pierre-Yves David's avatar
      dirstate-v2: freeze the on-disk format · bf11ff22a9af
      Pierre-Yves David authored
      It seems the format as reached a good balance. With a core of new capabilities
      that motivated it initially and enough new feature and room for future
      improvement to be a clear progress we can set a milestone for.
      
      Having the format frozen will help the feature to get real life testing, outside
      of the test suite.
      
      The feature itself stay experimental but the config gains a new name to avoid
      people enable non-frozen version by default.
      
      If too many bugs are reported during the RC we might move the format back to
      experimental and drop its support in future version (in favor of a new one)
      
      Differential Revision: https://phab.mercurial-scm.org/D11709
      bf11ff22a9af
  13. Nov 01, 2021
  14. Oct 22, 2021
  15. Oct 29, 2021
  16. Oct 28, 2021
    • Pierre-Yves David's avatar
      dirstate: make sure that status does not overlook the fallback flags · 500260410bb8
      Pierre-Yves David authored
      Without this extra checks, file with fallback flags change as the only change
      would be overlooked.
      
      In the future we might store proper data in the dirstate and do less lookup.
      However, for now this will do to make sure that 6.0 is forward compatible with
      later version.
      
      Differential Revision: https://phab.mercurial-scm.org/D11729
      500260410bb8
    • Pierre-Yves David's avatar
      dirstate: use a single closure for get_flags · 91f07430db8c
      Pierre-Yves David authored
      The previous code was overlooking fallback when neither symlink not exec was
      supported.
      
      The number of "variants" is getting too high, so I am consolidating this in a
      single closure that should be easier to maintains.
      
      This also ensure that fallback flags are always taken into account.
      
      (they are not user code yet, but small experimentation shown that the feature
      was working as intended.)
      
      A a small side effect we need to check for symlink support more lazily and this
      show up in the test in a couple of places.
      
      Differential Revision: https://phab.mercurial-scm.org/D11728
      91f07430db8c
  17. Apr 30, 2021
  18. Oct 26, 2021
  19. Oct 25, 2021
  20. Oct 23, 2021
  21. Oct 21, 2021
  22. Oct 20, 2021
Loading