diff hgext/largefiles/lfcommands.py @ 45455:b0d45612c552

largefiles: walk history in ascending order while downloading all lfiles

I don't think the order matters. Maybe it's purely because of the use of
walkchangerevs(), which was originally designed for "hg log" command.

Surprisingly, the number of objects fetched in test-largefiles.t has changed.
According to the --verbose output, the order of the following fetches flipped
and the latter got deduplicated.

  getting large3:eb7338044dc27f9bc59b8dd5a246b065ead7a9c4
  found eb7338044dc27f9bc59b8dd5a246b065ead7a9c4 in store
  getting sub/large4:eb7338044dc27f9bc59b8dd5a246b065ead7a9c4
  found eb7338044dc27f9bc59b8dd5a246b065ead7a9c4 in store

--- a/hgext/largefiles/lfcommands.py	Sun Sep 13 17:43:19 2020 +0900
+++ b/hgext/largefiles/lfcommands.py	Sun Sep 13 17:46:48 2020 +0900
@@ -489,7 +489,7 @@
     tonode = repo.changelog.node
     totalsuccess = 0
     totalmissing = 0
-    for rev in repo.revs(b'reverse(file(%s))', b'path:' + lfutil.shortname):
+    for rev in repo.revs(b'file(%s)', b'path:' + lfutil.shortname):
         success, missing = cachelfiles(ui, repo, tonode(rev))
         totalsuccess += len(success)
         totalmissing += len(missing)