mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

response

Browse source
This commit is contained in:
Joey Hess 2018-05-30 11:28:38 -04:00
parent b23c54fbb3
commit ecd534f1ee
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/forum/Migrate_from_one_connection_mechanism_for_special_remote_to_another/comment_1_6e8e3350ae26b6c59daa56b7e86cc46a._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-05-30T15:21:57Z"
content="""
Yes, there is an intermediate encryption key.
What may work is to use `git annex enableremote` on the original remote
with `externaltype=rclone`, which will make it use the other program.
Whether this will work depends on implementation details of both special
remotes. If they use the same names/urls/whatever to access the data stored
in them, it should work.
"""]]