From d4fff00142390c4a48ff6052a86823627920cbf8 Mon Sep 17 00:00:00 2001 From: "basile.pinsard@f1a7fae9f3bd9d5282fca11f62ad53b45a8eb317" Date: Wed, 16 Oct 2019 20:40:21 +0000 Subject: [PATCH 1/3] Added a comment --- ...nt_2_f66a8d597de5065049a9a9b245166540._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/slow_s3_transfer/comment_2_f66a8d597de5065049a9a9b245166540._comment diff --git a/doc/forum/slow_s3_transfer/comment_2_f66a8d597de5065049a9a9b245166540._comment b/doc/forum/slow_s3_transfer/comment_2_f66a8d597de5065049a9a9b245166540._comment new file mode 100644 index 0000000000..af4f64fb4f --- /dev/null +++ b/doc/forum/slow_s3_transfer/comment_2_f66a8d597de5065049a9a9b245166540._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="basile.pinsard@f1a7fae9f3bd9d5282fca11f62ad53b45a8eb317" + nickname="basile.pinsard" + avatar="http://cdn.libravatar.org/avatar/87e1f73acf277ad0337b90fc0253c62e" + subject="comment 2" + date="2019-10-16T20:40:21Z" + content=""" +Sorry for the late reply. + +Yes git-annex is CPU bound when downloading for instance. + +Could this just be the fact of using https for transfer? + +Thanks, I wouldn't have thought this to be the limitation. +"""]] From d533e59e734807efa36c66a844d3c462ccc5a528 Mon Sep 17 00:00:00 2001 From: irieger Date: Thu, 17 Oct 2019 09:07:26 +0000 Subject: [PATCH 2/3] Adding the question --- ..._40__some_parts_of__41___the_git_annex_tools.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools.mdwn diff --git a/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools.mdwn b/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools.mdwn new file mode 100644 index 0000000000..0ad353c4b9 --- /dev/null +++ b/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools.mdwn @@ -0,0 +1,12 @@ +Hello, + +at first I want to thank for the work on git annex. I started using git annex for managing my media files (digital photo and video data), which means loads of raw photographs and big video files that I have spread over some harddisks and need to keep track of locations and backups. Works quite well so far. + +A few years ago I build a small tool to offload camera memory cards with checksum/hash verification as it is common on film sets, copying all the content of the card and afterwards rereading and comparing all files to catch bitflips in transfer etc. All that while allowing copying to multiple target devices at the same time. + +I'd now like to include this workflow with git annex, allowing me to copy a memory card onto two or more annexed directories with this copy & verify workflow while using this hash directly for git annex and having both copies checked into annex at the end instead of like now copying and adding to annex afterwards. What would be an elegant solution? + +My naive thinking would be to move the file to the .git/annex/objects/ folder after hash creation and get it correctly registered in the annex management data somehow. Reason is to reduce the time consumed as I have the copy & verify anyway and would prefer to have it annex ready with as little overhead as possible. + +Cheers, +Ingmar From 10c9ba3430978de51e4298b361ff591b70c4698c Mon Sep 17 00:00:00 2001 From: "nrg@bd619d1ebf16e6324c546adea8be8fe1cc2b4325" Date: Thu, 17 Oct 2019 13:30:28 +0000 Subject: [PATCH 3/3] Added a comment: Issue is with persistent > 2.9.2 --- ...comment_1_f7cd45b9132e5929f216918b0c7fdb03._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/build_failure_on_macOS_10.14.6/comment_1_f7cd45b9132e5929f216918b0c7fdb03._comment diff --git a/doc/bugs/build_failure_on_macOS_10.14.6/comment_1_f7cd45b9132e5929f216918b0c7fdb03._comment b/doc/bugs/build_failure_on_macOS_10.14.6/comment_1_f7cd45b9132e5929f216918b0c7fdb03._comment new file mode 100644 index 0000000000..2c9b7ecf42 --- /dev/null +++ b/doc/bugs/build_failure_on_macOS_10.14.6/comment_1_f7cd45b9132e5929f216918b0c7fdb03._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="nrg@bd619d1ebf16e6324c546adea8be8fe1cc2b4325" + nickname="nrg" + avatar="http://cdn.libravatar.org/avatar/428b6c95b52769cf9eecdd351018eacb" + subject="Issue is with persistent > 2.9.2" + date="2019-10-17T13:30:28Z" + content=""" +The build issue is with a change in persistent >= 2.10.0. +persistent >= 2.8.1 && <= 2.9.2 resolves the build issue. +"""]]