git-annex/Remote
Joey Hess f44f715f51 ensure local remote is initialized when copying to it
Needed due to this scenario: Bare repo origin is made, foo is cloned from it;
foo is initalized; a file is added to foo's annex; git annex move --to origin

Since the git-annex branch has not yet been pushed to origin, it doesn't
auto-initialize. When the content is sent to it, it's stored, but
the remote has NoUUID, and so nothing is logged in the location log.
Then the content is removed from the local repo, and git-annex has lost
track of it.

git annex fsck in origin will find the lost content, but let's not let this
happen. Content should only be sent to initalized remotes.

This cannot happen for non-local remotes, since git-annex-shell always
checks that the repo is initialized.
2011-12-10 19:54:20 -04:00
..
Helper Fix caching of decrypted ciphers, which failed when drop had to check multiple different encrypted special remotes. 2011-12-08 16:01:46 -04:00
Bup.hs update 2011-12-10 18:51:01 -04:00
Directory.hs use lowercase hash by default; non-bare repos are a special case 2011-12-02 14:56:48 -04:00
Git.hs ensure local remote is initialized when copying to it 2011-12-10 19:54:20 -04:00
Hook.hs add support for using hashDirLower in addition to hashDirMixed 2011-11-28 22:43:51 -04:00
Rsync.hs factor out untilTrue 2011-12-02 16:12:31 -04:00
S3real.hs add support for using hashDirLower in addition to hashDirMixed 2011-11-28 22:43:51 -04:00
S3stub.hs fix building with S3 stub 2011-06-10 12:11:34 -04:00
Web.hs refactor 2011-12-03 09:10:23 -04:00