comparison tests/test-largefiles-misc.t @ 23741:f2893cd8d1e5

largefiles: pass a matcher instead of a raw file list to removelargefiles()

This is consistent with addlargefiles(), and will make it easier to get the
paths that are printed correct when recursing into subrepos or invoking from
outside the repository.  It also now restricts the path that the addremove is
performed on if a path is given, as is done with normal files.

The repo.status() call needs to exclude clean files when performing an
addremove, because the addremove override method calling this used to pass the
list of files to delete, which caused the matcher to only consider those files
in building the status list.  Now the matcher is restricted only to the extent
that the caller requested- usually directories if at all.  There's no reason for
addremove to care about clean files anyway- we don't want them deleted.

23740:9e1f4c65f5f5

  ? subrepo/normal.txt
  ? subrepo/renamed-large.txt
  $ mv subrepo/renamed-large.txt subrepo/large.txt
  $ hg -R subrepo add subrepo/normal.txt

  $ hg addremove
  adding large.dat as a largefile
  $ rm large.dat

  $ hg addremove
  removing large.dat

Lock in subrepo, otherwise the change isn't archived

  $ hg ci -S -m "add normal file to top level"

23741:f2893cd8d1e5

  ? subrepo/normal.txt
  ? subrepo/renamed-large.txt
  $ mv subrepo/renamed-large.txt subrepo/large.txt
  $ hg -R subrepo add subrepo/normal.txt

  $ hg addremove subrepo
  $ hg addremove -S
  adding large.dat as a largefile
  $ rm large.dat

  $ hg addremove subrepo
  $ hg addremove -S
  removing large.dat

Lock in subrepo, otherwise the change isn't archived

  $ hg ci -S -m "add normal file to top level"