drop --all cannot check numcopies from .gitattributes, so don't implement it!

I spent a long time worrying about this problem with --all, that it cannot
check .gitattributes files for numcopies settings, and so would not be
entirely safe to use. The solution turns out to be simple, just don't
implement `git annex drop --all`. drop is the only command that needs to
check numcopies (move can also reduce the number of copies, but explicitly
bypasses numcopies settings).

Use cases that might need a drop --all are probably better served by using
unused and dropunused, which already work in a bare repository.
This commit is contained in:
Joey Hess 2013-07-03 14:01:31 -04:00
parent b337a8b4c7
commit ebfd6fc2fe
2 changed files with 2 additions and 6 deletions

4
debian/changelog vendored
View file

@ -2,8 +2,8 @@ git-annex (4.20130628) UNRELEASED; urgency=low
* --all: New switch that makes git-annex operate on all data stored
in the git annex, including old versions of files. Supported by
fsck, get, drop, move, copy, migrate.
* get, drop, move, copy, migrate: Can now be run in a bare repository,
fsck, get, move, copy, migrate.
* get, move, copy, migrate: Can now be run in a bare repository,
like fsck already could. --all is enabled automatically in this case.
* webapp: Fix ssh setup with nonstandard port, broken in last release.

View file

@ -610,10 +610,6 @@ subdirectories).
normal behavior is to only operate on specified files in the working
tree.
Note that using --all makes .gitattributes annex.numcopies settings
not be honored. Other numcopies settings are still taken into account.
--all cannot be combined with --auto.
* --quiet
Avoid the default verbose display of what is done; only show errors