Skip to content
Snippets Groups Projects
  1. Feb 22, 2025
  2. Dec 11, 2023
    • Pierre-Yves David's avatar
      changelog: never inline changelog · dcaa2df1f688
      Pierre-Yves David authored
      The test suite mostly use small repositories, that implies that most changelog in the
      tests are inlined. As a result, non-inlined changelog are quite poorly tested.
      Since non-inline changelog are most common case for serious repositories, this
      lack of testing is a significant problem that results in high profile issue like
      the one recently fixed by 66417f55ea33 and 849745d7da89.
      
      Inlining the changelog does not bring much to the table, the number of total
      file saved is negligible, and the changelog will be read by most operation
      anyway.
      
      So this changeset is make it so we never inline the changelog, and de-inline the
      one that are still inlined whenever we touch them.
      
      By doing that, we remove the "dual code path" situation for writing new entry to
      the changelog and move to a "single code path" situation. Having a single
      code path simplify the code and make sure it is covered by test (if test cover
      that situation obviously)
      
      
      This impact all tests that care about the number of file and the exchange size,
      but there is nothing too complicated in them just a lot of churn.
      
      The churn is made "worse" by the fact rust will use the persistent nodemap on
      any changelog now. Which is overall a win as it means testing the persistent
      nodemap more and having less special cases.
      
      In short, having inline changelog is mostly useless and an endless source of
      pain. We get rid of it.
      dcaa2df1f688
  3. Mar 10, 2023
  4. May 02, 2022
    • Raphaël Gomès's avatar
      verify: also check dirstate · c84844cd523a
      Raphaël Gomès authored
      The dirstate already is capable of verifying its integrity (although v2
      features are not yet checked), let's run that code in `hg verify`.
      c84844cd523a
  5. Jan 22, 2020
    • Valentin Gatien-Baron's avatar
      recover: don't verify by default · 7a4e1d245f19
      Valentin Gatien-Baron authored
      The reason is:
      - it's not that hard to trigger interrupted transactions: just run out
        of disk space
      - it takes forever to verify on large repos. Before --no-verify, I
        told people to C-c hg recover when the progress bar showed up. Now I
        tell them to pass --no-verify.
      - I don't remember a single case where the verification step was
        useful
      
      This is technically a change of behavior. Perhaps this would be better
      suited for tweakdefaults?
      
      Differential Revision: https://phab.mercurial-scm.org/D7972
      7a4e1d245f19
  6. Dec 06, 2019
  7. Jan 26, 2019
  8. Nov 07, 2018
  9. Sep 19, 2018
  10. Sep 04, 2018
  11. Apr 04, 2018
  12. Jun 15, 2017
  13. Jun 20, 2017
  14. Sep 19, 2016
    • Martin von Zweigbergk's avatar
      strip: don't use "full" and "partial" to describe bundles · 769aee32fae0
      Martin von Zweigbergk authored
      The partial bundle is not a subset of the full bundle, and the full
      bundle is not full in any way that i see. The most obvious
      interpretation of "full" I can think of is that it has all commits
      back to the null revision, but that is not what the "full" bundle
      is. The "full" bundle is simply a backup of what the user asked us to
      strip (unless --no-backup). The "partial" bundle contains the
      revisions we temporarily stripped because they had higher revision
      numbers that some commit that the user asked us to strip.
      
      The "full" bundle is already called "backup" in the code, so let's use
      that in user-facing messages too. Let's call the "partial" bundle
      "temporary" in the code.
      769aee32fae0
  15. Feb 05, 2016
  16. Aug 06, 2014
  17. Nov 15, 2013
  18. Jun 10, 2012
    • kiilerix's avatar
      tests: add missing trailing 'cd ..' · f2719b387380
      kiilerix authored
      Many tests didn't change back from subdirectories at the end of the tests ...
      and they don't have to. The missing 'cd ..' could always be added when another
      test case is added to the test file.
      
      This change do that tests (99.5%) consistently end up in $TESTDIR where they
      started, thus making it simpler to extend them or move them around.
      f2719b387380
  19. Nov 07, 2011
  20. Apr 29, 2011
Loading