From 53803d444716108a8cf4f0720b3d8d0e08471b48 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U" Date: Sun, 7 Jul 2013 09:02:10 +0000 Subject: --- ...git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn index ff4a1f56f..e1a4d049c 100644 --- a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn +++ b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn @@ -7,3 +7,5 @@ Two basic modes of operation: * If run on another indirect annex, it would copy over the symlinks, copy over the object data, verify that the checksums are OK and add to the annex An optional `git annex import --copy-only` would copy over and verify the data, but not yet add it. That would allow the user to import into a decent data structure. If run on non-annexed data, `git annex import --copy-only` would ideally calculate checksums and create symlinks already; thus ensuring data integrity as early as possible. + +-- RichiH -- cgit v1.2.3