diff options
| author |  Joey Hess <joey@kitenet.net> | 2012-01-19 15:24:05 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2012-01-19 15:24:05 -0400 |
| commit | 90319afa41ca6d8a9ffe00d787dc3dcdff320f00 (patch) | |
| tree | 68b9a324b9feb7ed45cc7ab24dc82e120cc26ff3 /debian | |
| parent | d36525e9745b90cc04abfeac6500ff646cb9c89b (diff) | |
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!
Diffstat (limited to 'debian')
| -rw-r--r-- | debian/changelog | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/debian/changelog b/debian/changelog index d6c4419bb..684993148 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,16 @@ +git-annex (3.20120117) UNRELEASED; urgency=low + + * 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. 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! + + -- Joey Hess <joeyh@debian.org> Thu, 19 Jan 2012 15:12:03 -0400 + git-annex (3.20120116) unstable; urgency=medium * Fix data loss bug in directory special remote, when moving a file |