1. 15 Jan, 2020 1 commit
  2. 28 Dec, 2019 1 commit
    • tests: stabilize test-subrepo-svn.t on Windows · e598c874b4a
      This partially reverts 991e4404e910, because the URL form of `C:\...` gets
      escaped to `C%3A/...`, which breaks the substitution of $TESTTMP.
      
      The forget command on 'notafile*' errored out with:
      
         notafile*: The filename, directory name, or volume label syntax is incorrect
      
      which I think is because '*' isn't a legal character in a file name (though I
      can't trigger this directly from MSYS or cmd.exe for some reason).
      
      Differential Revision: https://phab.mercurial-scm.org/D7816
      Matt Harbison authored
  3. 13 Jan, 2020 2 commits
  4. 30 Dec, 2019 1 commit
  5. 27 Dec, 2019 2 commits
    • graftcopies: remove `skip` and `repo` arguments · 833210fbd90
      The `skip` argument was added in 2ba6c9b4e0eb (rebase: fix bug that
      caused transitive copy records to disappear (issue4192), 2014-06-07)
      in order to fix https://bz.mercurial-scm.org/show_bug.cgi?id=4192. I
      ran tests at that commit without the `skiprev` argument and the only
      difference I noticed was that `test-rebase-collapse.t` failed
      differently, in the call that is now on line 501. Without the
      `skiprev` argument, that call would end up creating another commit
      because it tried to record an invalid copy. With the previous patch in
      this series, such invalid copies are no longer recorded, so it seems
      we don't need the `skip` argument anymore.
      
      I also removed the `repo` argument since that also becomes unused with
      the removal of the `skip` argument.
      
      Differential Revision: https://phab.mercurial-scm.org/D7860
      Martin von Zweigbergk authored
    • graftcopies: use _filter() for filtering out invalid copies · 3df0bd706c4
      `graftcopies()` (formerly called `duplicatecopies()`) checked that the
      copy destination existed in the working copy, but it didn't check that
      copy source existed in the parent of the working copy. In
      `test-graft.t` we can see that as warnings about not finding ancestors
      of the copied files, and also empty commits getting created.
      
      This patch uses the existing `_filter()` function for filtering out
      invalid copies. In addition to the aforementioned types, that also
      includes copies where source and destination is the same.
      
      Differential Revision: https://phab.mercurial-scm.org/D7859
      Martin von Zweigbergk authored
  6. 06 Jan, 2020 1 commit
  7. 27 Dec, 2019 1 commit
  8. 15 Jan, 2020 4 commits
  9. 14 Jan, 2020 1 commit
  10. 15 Jan, 2020 3 commits
  11. 14 Jan, 2020 7 commits
  12. 23 Dec, 2019 2 commits
    • verify: allow the storage to signal when renames can be tested on `skipread` · b9e174d4ed1
      This applies the new marker in the lfs handler to show it in action, and adds
      the test mentioned at the beginning of the series to show that fulltext isn't
      necessary in the LFS case.
      
      The existing `skipread` isn't enough, because it is also set if an error occurs
      reading the revlog data, or the data is censored.  It could probably be cleared,
      but then it technically violates the interface contract.  That wouldn't matter
      for the existing verify algorithm, but it isn't clear how that will change as
      alternate storage support is added.
      
      The flag is probably pretty revlog specific, given the comments in verify.py.
      But there's already filelog specific stuff in there and I'm not sure what future
      storage will bring, so I don't want to over-engineer this.  Likewise, I'm not
      sure that we want the verify method for each storage type to completely drive
      the bus when it comes to detecting renames, so I don't want to go down the
      rabbithole of having verifyintegrity() return metadata hints at this point.
      
      Differential Revision: https://phab.mercurial-scm.org/D7713
      Matt Harbison authored
    • lfs: don't skip locally available blobs when verifying · 1a6dd50cd0d
      The `skipflags` config was introduced in a2ab9ebcd85b, which specifically calls
      out downloading and storing all blobs as potentially too expensive.  But I don't
      see any reason to skip blobs that are already available locally.  Hashing the
      blob is the only way to indirectly verify the rawdata content stored in the
      revlog.
      
      (The note in that commit about skipping renamed is still correct, but the reason
      given about needing fulltext isn't.)
      
      Differential Revision: https://phab.mercurial-scm.org/D7712
      Matt Harbison authored
  13. 20 Dec, 2019 1 commit
  14. 08 Jan, 2020 2 commits
  15. 07 Dec, 2019 2 commits
  16. 14 Jan, 2020 3 commits
  17. 13 Jan, 2020 5 commits
  18. 08 Jan, 2020 1 commit