From 0822ee52ddb6bbb0266edaf23c53676706249f37 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 19 Nov 2019 17:39:47 +0000 Subject: [PATCH 1/2] Added a comment: import/export --- ...comment_2_f2d436822490e74544bf58a4f1c9ee79._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/todo/change_git-annex-import_not_to_delete_original_files_by_default/comment_2_f2d436822490e74544bf58a4f1c9ee79._comment diff --git a/doc/todo/change_git-annex-import_not_to_delete_original_files_by_default/comment_2_f2d436822490e74544bf58a4f1c9ee79._comment b/doc/todo/change_git-annex-import_not_to_delete_original_files_by_default/comment_2_f2d436822490e74544bf58a4f1c9ee79._comment new file mode 100644 index 0000000000..c4c86551d8 --- /dev/null +++ b/doc/todo/change_git-annex-import_not_to_delete_original_files_by_default/comment_2_f2d436822490e74544bf58a4f1c9ee79._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="import/export" + date="2019-11-19T17:39:47Z" + content=""" +Makes sense. It's certainly better if import/export did complementary things. Maybe, move the old `git-annex-import` functionality to a new command called `git-annex-ingest`? + +\"everything not involving importing from a special remote should be deprecated\" -- i.e. to ingest a directory you'd first create a directory special remote for it, and then `git-annex-import` from that? +"""]] From 3e4b5d2d9390780fdb4f917815feb3f648ab4ef4 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 19 Nov 2019 17:51:08 +0000 Subject: [PATCH 2/2] Added a comment: using hardlinks --- ...mment_3_ee247d9316df963fd584df2199b80fe2._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/How_to_prevent_copies_on_a_single_device_and_use_only_hardlinks/comment_3_ee247d9316df963fd584df2199b80fe2._comment diff --git a/doc/forum/How_to_prevent_copies_on_a_single_device_and_use_only_hardlinks/comment_3_ee247d9316df963fd584df2199b80fe2._comment b/doc/forum/How_to_prevent_copies_on_a_single_device_and_use_only_hardlinks/comment_3_ee247d9316df963fd584df2199b80fe2._comment new file mode 100644 index 0000000000..d272eb88a1 --- /dev/null +++ b/doc/forum/How_to_prevent_copies_on_a_single_device_and_use_only_hardlinks/comment_3_ee247d9316df963fd584df2199b80fe2._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="using hardlinks" + date="2019-11-19T17:51:08Z" + content=""" +I again don't have a full answer, but maybe you could customize git's [post-checkout hook](https://git-scm.com/docs/githooks#_post_checkout)? (You'd need to still call the hook that git-annex installs.) + +Also, I've thrown together a [[FUSE filesystem|https://github.com/broadinstitute/viral-ngs/blob/is-dx-benchmarks/tools/git-annex-remotes/git-annex-on-demand.py]] that fetches git-annexed files on demand, maybe that could be adapted. It only works with locked files and symlinks though. + +What is the reason you don't want to use locked files? You can have different [[worktrees|tips/Using_git-worktree_with_annex]] with symlinks of locked files pointing into the same annex. +"""]]