From 227206c089f8ec45465c92e9c907e65b03ccad17 Mon Sep 17 00:00:00 2001 From: "lykos@d125a37d89b1cfac20829f12911656c40cb70018" Date: Thu, 6 Feb 2020 06:56:41 +0000 Subject: [PATCH] --- ...-encrypt_when_key_is_already_in_.git__47__annex__47__tmp.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/todo/Don__39__t_re-encrypt_when_key_is_already_in_.git__47__annex__47__tmp.mdwn diff --git a/doc/todo/Don__39__t_re-encrypt_when_key_is_already_in_.git__47__annex__47__tmp.mdwn b/doc/todo/Don__39__t_re-encrypt_when_key_is_already_in_.git__47__annex__47__tmp.mdwn new file mode 100644 index 0000000000..6a461cffff --- /dev/null +++ b/doc/todo/Don__39__t_re-encrypt_when_key_is_already_in_.git__47__annex__47__tmp.mdwn @@ -0,0 +1 @@ +I've implemented true resumable upload in git-annex-remote-googledrive which means that uploads can, just as downloads, be resumed at any point, even within one chunk. However, it currently does not work with encrypted files (or chunks) due to the non-deterministic nature of GPG. In order to make this feature useable on encrypted files, I propose to not overwrite encrypted files which are already present inside the `tmp` directory.