diff options
author | https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web> | 2013-07-07 09:01:40 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2013-07-07 09:01:40 +0000 |
commit | d74736b20d1676bad54ee1850020e08b2d067c5f (patch) | |
tree | facc1488b8a9c9ba7f0f3604c99f82b0684274f3 | |
parent | d00206da7a81972847f9ed7ba4dbbaabb80bbc69 (diff) |
-rw-r--r-- | doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn | 9 |
1 files changed, 9 insertions, 0 deletions
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 new file mode 100644 index 000000000..ff4a1f56f --- /dev/null +++ b/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn @@ -0,0 +1,9 @@ +`git annex import` would copy data over from external places into the annex. It would be run from within the annex and in the target location where the files need to end up. + +Two basic modes of operation: + +* If run on a normal directory, e.g. an SD card, it would simply copy over and `git annex add $newstuff` + +* 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. |