diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-09-18 12:55:20 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-09-18 12:55:20 -0400 |
| commit | c38ef538bfa0fe13acbc3403ab23c8857f2a52e5 (patch) | |
| tree | 44254a9221bfb471870d79fee7bca2b0703eaae7 | |
| parent | f4b81327f5c4caf66305100007bc1873f06bd02f (diff) | |
comment
| -rw-r--r-- | doc/forum/Backend_migration_and_special_remotes/comment_1_cf6d45c43b14719fc5ea41d0cbfb612d._comment | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/Backend_migration_and_special_remotes/comment_1_cf6d45c43b14719fc5ea41d0cbfb612d._comment b/doc/forum/Backend_migration_and_special_remotes/comment_1_cf6d45c43b14719fc5ea41d0cbfb612d._comment new file mode 100644 index 000000000..877594007 --- /dev/null +++ b/doc/forum/Backend_migration_and_special_remotes/comment_1_cf6d45c43b14719fc5ea41d0cbfb612d._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-09-18T16:47:02Z" + content=""" +A rename operation could be added to the interface for remotes. I suspect +most remotes wouldn't be able to implement it (could hubic?), but it could +be used when available. + +I'm not sure what to do in the migrate command to make it use such an +interface though. It could try to move the files to their new names on each +remote that supports the interface. But what about remotes that cannot be +accessed? + +Could make a `git annex migrate --on remote`, to +migrate remotes peicemeal. Which would have to look back in the git history +to find the old key that a file had been migrated from. +Although then the user has to be careful to specify the same set of +files that were migrated before. +"""]] |