From d57751f51c8e7067762b4cf73d1970b1b7e7648c Mon Sep 17 00:00:00 2001 From: irieger Date: Tue, 22 Oct 2019 06:23:21 +0000 Subject: [PATCH 1/9] Added a comment: comment 3 --- ..._39f0ea1349cdea103d70375263bbfd4a._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment diff --git a/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment b/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment new file mode 100644 index 0000000000..183d7c7dda --- /dev/null +++ b/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="irieger" + avatar="http://cdn.libravatar.org/avatar/83622f3c2fedea51e69f9a3986f95d73" + subject="comment 3" + date="2019-10-22T06:23:20Z" + content=""" +Hey, thanks for those comments. + +tried joeys example in a small test repo but will repeat it with some real image data (on copies of course). + +Just two more things: +1. + KEY=SHA1-s11--x + OBJECT=$(git annex examinekey $KEY --format='.git/annex/objects/${hashdirmixed}${key}/${key}') + + ln -s $OBJECT foo + git add foo + git -c annex.verify=false annex setkey $KEY /mnt/foo +"""]] From 4865102572c2615be3ad8b3415908faaffe735a1 Mon Sep 17 00:00:00 2001 From: irieger Date: Tue, 22 Oct 2019 06:54:44 +0000 Subject: [PATCH 2/9] Added a comment: comment 3 --- ..._7d9d45716e9e847f3bde214949796222._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_4_7d9d45716e9e847f3bde214949796222._comment diff --git a/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_4_7d9d45716e9e847f3bde214949796222._comment b/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_4_7d9d45716e9e847f3bde214949796222._comment new file mode 100644 index 0000000000..8b94b6661c --- /dev/null +++ b/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_4_7d9d45716e9e847f3bde214949796222._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="irieger" + avatar="http://cdn.libravatar.org/avatar/83622f3c2fedea51e69f9a3986f95d73" + subject="comment 3" + date="2019-10-22T06:54:43Z" + content=""" +Hey, thank you for those comments. + +Tried your example joey and it seems to do exactly what I was thinking of. Now I have the roadmap I will adapt my tool to. + +Just a few more small questions: + +1.) How can I trigger the *(recording state in git...)* after throwing in files with *git -c annex.verify=false -c annex.alwayscommit=false annex setkey ...*? + +2.) Can setkey be used on multiple repositories for the same file and then have the file exists in multiple copies after this without an *annex copy*? (Of course only one symlink generation and *git add*) + +So thanks again for the fast replies. + +-- Ingmar +"""]] From ffbf205ab619edb7cc9b41cccbe96f94c25ade3e Mon Sep 17 00:00:00 2001 From: irieger Date: Tue, 22 Oct 2019 06:55:20 +0000 Subject: [PATCH 3/9] removed --- ..._39f0ea1349cdea103d70375263bbfd4a._comment | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment diff --git a/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment b/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment deleted file mode 100644 index 183d7c7dda..0000000000 --- a/doc/forum/Is_it_possible_adding_files_to_git_annex_bypassing___40__some_parts_of__41___the_git_annex_tools/comment_3_39f0ea1349cdea103d70375263bbfd4a._comment +++ /dev/null @@ -1,19 +0,0 @@ -[[!comment format=mdwn - username="irieger" - avatar="http://cdn.libravatar.org/avatar/83622f3c2fedea51e69f9a3986f95d73" - subject="comment 3" - date="2019-10-22T06:23:20Z" - content=""" -Hey, thanks for those comments. - -tried joeys example in a small test repo but will repeat it with some real image data (on copies of course). - -Just two more things: -1. - KEY=SHA1-s11--x - OBJECT=$(git annex examinekey $KEY --format='.git/annex/objects/${hashdirmixed}${key}/${key}') - - ln -s $OBJECT foo - git add foo - git -c annex.verify=false annex setkey $KEY /mnt/foo -"""]] From 4175d50d4bcfc7872ef944a08c38fa151291020c Mon Sep 17 00:00:00 2001 From: leej Date: Tue, 22 Oct 2019 07:21:31 +0000 Subject: [PATCH 4/9] Added a comment: +1 to the comments above --- .../comment_20_e6f9f112819b7dd54604eef079cc86cd._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/lets_discuss_git_add_behavior/comment_20_e6f9f112819b7dd54604eef079cc86cd._comment diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_20_e6f9f112819b7dd54604eef079cc86cd._comment b/doc/forum/lets_discuss_git_add_behavior/comment_20_e6f9f112819b7dd54604eef079cc86cd._comment new file mode 100644 index 0000000000..f755d8f1e7 --- /dev/null +++ b/doc/forum/lets_discuss_git_add_behavior/comment_20_e6f9f112819b7dd54604eef079cc86cd._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="leej" + avatar="http://cdn.libravatar.org/avatar/eb1c6bd57680f694fb4658388e6de4ed" + subject="+1 to the comments above" + date="2019-10-22T07:21:31Z" + content=""" +Git Annex has been and is a terrific tool. And, I would, very respectfully, like to +1 the comments above. I agree with spwhitton that v7 `git add` behavior would benefit from being off by default, with a way to turn it on as required. Both from a migration safety/friction-reduction standpoint, but also from the least invasive integration with Git principle that amindfv and others have so well articulated. +"""]] From ebb893a1773ce49a897a70cf26d355058c8e04e0 Mon Sep 17 00:00:00 2001 From: CandyAngel Date: Tue, 22 Oct 2019 08:18:31 +0000 Subject: [PATCH 5/9] Added a comment --- ...mment_6_79c5821a38ed3b5bd97ca676b130e7d3._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_6_79c5821a38ed3b5bd97ca676b130e7d3._comment diff --git a/doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_6_79c5821a38ed3b5bd97ca676b130e7d3._comment b/doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_6_79c5821a38ed3b5bd97ca676b130e7d3._comment new file mode 100644 index 0000000000..11c2b28fc3 --- /dev/null +++ b/doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_6_79c5821a38ed3b5bd97ca676b130e7d3._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="CandyAngel" + avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8" + subject="comment 6" + date="2019-10-22T08:18:31Z" + content=""" +> unwarranted and unhelpful to drag discussion of it into a question like this + +*..what?* + +This sort of question is *exactly the right place* to warn a user the thing they are asking about is an *irreversible change* that fundamentally changes how their annexes will work when interacted with, even when not using `git-annex` commands. +"""]] From 74ee2386714de4de6f7b8954103ae67108ad1dd3 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 22 Oct 2019 16:33:22 +0000 Subject: [PATCH 6/9] Added a comment: temporary manual downgrade of repos to v5 is possible --- ...mment_21_ca9acb1dac5ec6762caed585be21fd9c._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment b/doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment new file mode 100644 index 0000000000..7ef82f0232 --- /dev/null +++ b/doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="temporary manual downgrade of repos to v5 is possible" + date="2019-10-22T16:33:22Z" + content=""" +Related: until the v7 issues are resolved, one option is to manually [downgrade](forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/#comment-e1a252807a2200a7c737696abd08d38b) the repos to v5 (turns out it only involves changing a few git config and gitattributes settings) and use an [[pre-7.20190912|news/version_7.20190819]] git-annex version. + +Just to reiterate, I much appreciate @joeyh's work on v7 and [[think|lets_discuss_git_add_behavior/#comment-ffd69d3a710beeac091ef4173b122cdc]] it's an important advance. The v5 downgrade is just a temp option to keep old workflows working, until they can be adapted to v7, which won't be hard to do once the issues discussed above get addressed. + +"""]] From 00b1beb41b9f4ae0d0299bbf9656544dcd5e55ca Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 22 Oct 2019 16:35:15 +0000 Subject: [PATCH 7/9] removed --- ...mment_21_ca9acb1dac5ec6762caed585be21fd9c._comment | 11 ----------- 1 file changed, 11 deletions(-) delete mode 100644 doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment b/doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment deleted file mode 100644 index 7ef82f0232..0000000000 --- a/doc/forum/lets_discuss_git_add_behavior/comment_21_ca9acb1dac5ec6762caed585be21fd9c._comment +++ /dev/null @@ -1,11 +0,0 @@ -[[!comment format=mdwn - username="Ilya_Shlyakhter" - avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" - subject="temporary manual downgrade of repos to v5 is possible" - date="2019-10-22T16:33:22Z" - content=""" -Related: until the v7 issues are resolved, one option is to manually [downgrade](forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/#comment-e1a252807a2200a7c737696abd08d38b) the repos to v5 (turns out it only involves changing a few git config and gitattributes settings) and use an [[pre-7.20190912|news/version_7.20190819]] git-annex version. - -Just to reiterate, I much appreciate @joeyh's work on v7 and [[think|lets_discuss_git_add_behavior/#comment-ffd69d3a710beeac091ef4173b122cdc]] it's an important advance. The v5 downgrade is just a temp option to keep old workflows working, until they can be adapted to v7, which won't be hard to do once the issues discussed above get addressed. - -"""]] From cf2d18a568470455b2f2051928b4a1785af30cfe Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 22 Oct 2019 16:40:32 +0000 Subject: [PATCH 8/9] Added a comment: temporary manual downgrade of repos to v5 is possible --- ...omment_21_d44ea6ad7f342eb649b2e1024c6667b4._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/lets_discuss_git_add_behavior/comment_21_d44ea6ad7f342eb649b2e1024c6667b4._comment diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_21_d44ea6ad7f342eb649b2e1024c6667b4._comment b/doc/forum/lets_discuss_git_add_behavior/comment_21_d44ea6ad7f342eb649b2e1024c6667b4._comment new file mode 100644 index 0000000000..ddf01bdd7a --- /dev/null +++ b/doc/forum/lets_discuss_git_add_behavior/comment_21_d44ea6ad7f342eb649b2e1024c6667b4._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="temporary manual downgrade of repos to v5 is possible" + date="2019-10-22T16:40:32Z" + content=""" +Related: until the v7 issues are resolved, one option is to manually [downgrade](https://git-annex.branchable.com/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/#comment-e1a252807a2200a7c737696abd08d38b) the repos to v5 (turns out it only involves changing a few git config and gitattributes settings) and use an [[pre-7.20190912|news/version_7.20190819]] git-annex version. + +Just to reiterate, I much appreciate @joeyh's work on v7 and [[think|forum/lets_discuss_git_add_behavior/#comment-ffd69d3a710beeac091ef4173b122cdc]] it's an important advance. The v5 downgrade is just a temp option to keep old workflows working, until they can be adapted to v7, which won't be hard to do once the issues discussed above get addressed. +"""]] From 48999a3caf0bc6b9c6e5a1043ab5fc531f9b0e14 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 22 Oct 2019 18:25:11 +0000 Subject: [PATCH 9/9] Added a comment: locking files before reverting to v5 --- .../comment_7_cec779ef77336ea30728815739be78b6._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_7_cec779ef77336ea30728815739be78b6._comment diff --git a/doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_7_cec779ef77336ea30728815739be78b6._comment b/doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_7_cec779ef77336ea30728815739be78b6._comment new file mode 100644 index 0000000000..1e57c27644 --- /dev/null +++ b/doc/forum/Exactly_what_does_a_v5_to_v7_upgrade_entail__63__/comment_7_cec779ef77336ea30728815739be78b6._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="locking files before reverting to v5" + date="2019-10-22T18:25:11Z" + content=""" +\"It is entirely reversable by undoing the git config changes\" -- just to note, before undoing the git config changes, you'd want to [[lock|git-annex-lock]] any unlocked files (after first committing any pending changes to them). +"""]]