diff options
| author |  Joey Hess <joey@kitenet.net> | 2014-02-20 15:36:59 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2014-02-20 15:36:59 -0400 |
| commit | 50a16be7d669cc712f212168ba65de99c0e96c8e (patch) | |
| tree | 73848d2d185aa840cf98981cb4f509edfde46c47 | |
| parent | f4e15e72fb12666edeefd961414c723891d84be2 (diff) | |
Revert "Fix command to match fsck description"
This reverts commit 5c9b7b524474fa6deac38d24bac9781557760253.
No, --incremental and --more are not needed when using
--incremental-schedule. The --incremental-schedule option
implies the other ones.
| -rw-r--r-- | doc/git-annex.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/git-annex.mdwn b/doc/git-annex.mdwn index 87eeda4fd..7b1ac928b 100644 --- a/doc/git-annex.mdwn +++ b/doc/git-annex.mdwn @@ -517,7 +517,7 @@ subdirectories). have been fscked. And once it's done, you'd like a new fsck pass to start, but no more often than once a month. Then put this in a nightly cron job: - git annex fsck --incremental --more --incremental-schedule 30d --time-limit 5h + git annex fsck --incremental-schedule 30d --time-limit 5h To verify data integrity only while disregarding required number of copies, use `--numcopies=1`. |