diff options
| author |  https://www.google.com/accounts/o8/id?id=AItOawkSq2FDpK2n66QRUxtqqdbyDuwgbQmUWus <Jimmy@web> | 2011-03-24 18:38:38 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2011-03-24 18:38:38 +0000 |
| commit | bc5f5428d39459228f61ec2e164bcbd00e110593 (patch) | |
| tree | 0fd91492b8ae34191b991b339265a8c678d4909d | |
| parent | 0ed90ae99246c44a36c8956124c1c645cb845809 (diff) | |
| -rw-r--r-- | doc/forum/Behaviour_of_fsck.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/Behaviour_of_fsck.mdwn b/doc/forum/Behaviour_of_fsck.mdwn index 29aa3ec64..cd27d49f7 100644 --- a/doc/forum/Behaviour_of_fsck.mdwn +++ b/doc/forum/Behaviour_of_fsck.mdwn @@ -1,4 +1,4 @@ -The current behaviour of 'fsck' is a bit verbose. I have an annex'd directory of tarballs for my own build system for "science" applications, there's about ~600 or blobs in my repo, I do occassionally like to run fsck across all my data to see what files don't meet the min num copies requirement that I have set. +The current behaviour of 'fsck' is a bit verbose. I have an annex'd directory of tarballs for my own build system for "science" applications, there's about ~600 or so blobs in my repo, I do occassionally like to run fsck across all my data to see what files don't meet the min num copies requirement that I have set. Would it be better for the default behaviour of fsck when it has not been given a path to only output errors and not bother to show that a file is ok for every single file in a repo. i.e. |