From 599d438fa629a032725fa93f247e8460f8a88b2d Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 11 Oct 2019 16:23:08 +0000 Subject: [PATCH 1/2] Added a comment --- ...comment_2_d7f2a6de08a3559a1d76ae8aba5a6702._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/todo/reinit_current_repo_to_new_uuid/comment_2_d7f2a6de08a3559a1d76ae8aba5a6702._comment diff --git a/doc/todo/reinit_current_repo_to_new_uuid/comment_2_d7f2a6de08a3559a1d76ae8aba5a6702._comment b/doc/todo/reinit_current_repo_to_new_uuid/comment_2_d7f2a6de08a3559a1d76ae8aba5a6702._comment new file mode 100644 index 0000000000..3a4150e70e --- /dev/null +++ b/doc/todo/reinit_current_repo_to_new_uuid/comment_2_d7f2a6de08a3559a1d76ae8aba5a6702._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 2" + date="2019-10-11T16:23:08Z" + content=""" +>You would probably also want to run git annex fsck --fast so that any annexed content in the repo gets recorded as being present in the new uuid + +This takes very long on my repo, even with `--fast`. Maybe, there's a way to make a fast dedicated command for this scenario? Or, a version of [[sameas|todo/support_multiple_special_remotes_with_same_uuid/]] which represents the fact that all presence info in this repo *up to this timestamp* is same as in old repo, but from that point on this repo is separate? +"""]] From 8432c3912f444af64f267eafd0b4cd185940ddee Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 11 Oct 2019 16:38:07 +0000 Subject: [PATCH 2/2] Added a comment: preventing inadvertently adding annexed files in unlocked form --- ...mment_2_0989d05a27ba8a56787bc5dbe581d1ae._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/todo/addunlocked_config_setting/comment_2_0989d05a27ba8a56787bc5dbe581d1ae._comment diff --git a/doc/todo/addunlocked_config_setting/comment_2_0989d05a27ba8a56787bc5dbe581d1ae._comment b/doc/todo/addunlocked_config_setting/comment_2_0989d05a27ba8a56787bc5dbe581d1ae._comment new file mode 100644 index 0000000000..e5e8e030ff --- /dev/null +++ b/doc/todo/addunlocked_config_setting/comment_2_0989d05a27ba8a56787bc5dbe581d1ae._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="preventing inadvertently adding annexed files in unlocked form" + date="2019-10-11T16:38:07Z" + content=""" +> It is not possible for git add to add files in locked form. git's interface simply does not allow that. + +Makes sense. Then, [[separate annex.largefiles.git-add and annex.largefiles.git-annex-add settings]] seems like the way to prevent inadvertently adding files to annex in unlocked form. + +Related: [[todo/auto-lock_files_after_one_edit]] +"""]]