diff options
author | Joey Hess <joey@kitenet.net> | 2010-11-15 18:37:49 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2010-11-15 18:37:49 -0400 |
commit | 0893820812c9cc10287c861dccbdae3c287cd7cf (patch) | |
tree | 3d3216d68f805d84ce423244273fee8f4e8353a3 /doc | |
parent | a5e7f5329f4d9a80a34302e3707f0bd42b91a441 (diff) |
fsck: Print warnings to stderr; --quiet can now be used to only see problems.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/walkthrough.mdwn | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/walkthrough.mdwn b/doc/walkthrough.mdwn index a1a888242..281f46050 100644 --- a/doc/walkthrough.mdwn +++ b/doc/walkthrough.mdwn @@ -296,7 +296,7 @@ eliminate it to save space. 2 WORM:1289672605:14:file (To see where data was previously used, try: git log --stat -S'KEY') (To remove unwanted data: git-annex dropunused NUMBER) - failed + ok After running `git annex unused`, you can follow the instructions to examine the history of files that used the data, and if you decide you don't need that @@ -316,7 +316,7 @@ setting is satisfied for all files. # git annex fsck unused (checking for unused data...) ok fsck my_cool_big_file (checksum...) ok - ...... + ... You can also specifiy the files to check. This is particularly useful if you're using sha1 and don't want to spend a long time checksumming everything. @@ -332,10 +332,10 @@ might say about a badly messed up annex: # git annex fsck fsck my_cool_big_file (checksum...) - Bad file content; moved to .git/annex/bad/SHA1:7da006579dd64330eb2456001fd01948430572f2 - ** No known copies of the file exist! + git-annex: Bad file content; moved to .git/annex/bad/SHA1:7da006579dd64330eb2456001fd01948430572f2 + git-annex: ** No known copies of the file exist! failed fsck important_file - Only 1 of 2 copies exist. Run git annex get somewhere else to back it up. + git-annex: Only 1 of 2 copies exist. Run git annex get somewhere else to back it up. failed git-annex: 2 failed |