From a380fb00a224a9277cd3464a9443fd4382a687b8 Mon Sep 17 00:00:00 2001 From: "git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" Date: Thu, 2 Mar 2017 16:14:52 +0000 Subject: Added a comment --- .../comment_1_01363d4b41dcbebc9bcff7b956c03091._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment (limited to 'doc') diff --git a/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment new file mode 100644 index 000000000..c04f2f4eb --- /dev/null +++ b/doc/todo/wishlist__58___Parity_files_for_encrypted_remotes/comment_1_01363d4b41dcbebc9bcff7b956c03091._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="git-annex@31849d241f10c295b30a9707352ae5c7d743adb7" + nickname="git-annex" + avatar="http://cdn.libravatar.org/avatar/180f1a763647bfc099e97ac88b8f7b37" + subject="comment 1" + date="2017-03-02T16:14:51Z" + content=""" +If you're generating parity files for the content anyway, why not encrypt locally, generate parity files for the encrypted content, then check that in to git-annex? +"""]] -- cgit v1.2.3