use --more rather than --new to continue incremental fsck
This commit is contained in:
parent
e855cffa1b
commit
ed93d662d3
2 changed files with 2 additions and 2 deletions
|
@ -43,7 +43,7 @@ startIncrementalOption :: Option
|
|||
startIncrementalOption = Option.flag ['S'] "incremental" "start an incremental fsck"
|
||||
|
||||
incrementalOption :: Option
|
||||
incrementalOption = Option.flag ['n'] "new" "continue an incremental fsck"
|
||||
incrementalOption = Option.flag ['m'] "more" "continue an incremental fsck"
|
||||
|
||||
options :: [Option]
|
||||
options = [fromOption, startIncrementalOption, incrementalOption]
|
||||
|
|
|
@ -260,7 +260,7 @@ subdirectories).
|
|||
To check a remote to fsck, specify --from.
|
||||
|
||||
To start a new incremental fsck, specify --incremental. Then
|
||||
the next time you fsck, you can specify --new to skip over
|
||||
the next time you fsck, you can specify --more to skip over
|
||||
files that have already been checked, and continue where it left off.
|
||||
|
||||
To avoid expensive checksum calculations (and expensive transfers when
|
||||
|
|
Loading…
Add table
Reference in a new issue