Joey Hess 90319afa41 fsck --from ... Fscking a remote is now supported. It's done by retrieving the contents of the specified files from the remote, and checking them, so can be an expensive operation. (Several optimisations are possible, to speed it up, of course.. This is the slow and stupid remote fsck to start with.) Still, if the remote is a special remote, or a git repository that you cannot run fsck in locally, it's nice to have the ability to fsck it. If you have any directory special remotes, now would be a good time to fsck them, in case you were hit by the data loss bug fixed in the previous release!		2012-01-19 15:24:05 -04:00
..
Backend.hs	fsck --from	2012-01-19 15:24:05 -04:00
BranchState.hs	avoid multiple unnecessary stats of the index file	2012-01-14 12:07:36 -04:00
Command.hs	tweak	2012-01-06 10:57:57 -04:00
Crypto.hs	split out Utility.Gpg with the generic gpg interface, from Crypto	2011-12-20 23:24:06 -04:00
Key.hs	factor out common imports	2011-10-03 23:29:48 -04:00
Option.hs	per-command options	2012-01-05 23:11:07 -04:00
Remote.hs	fix comment	2011-12-31 04:14:33 -04:00
TrustLevel.hs	dead: A command which says that a repository is gone for good and you don't want git-annex to mention it again.	2011-12-02 16:59:55 -04:00
UUID.hs	clean up read/show abuse	2011-11-08 00:17:54 -04:00