diff options
Diffstat (limited to 'doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn')
| -rw-r--r-- | doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn | 13 |
1 files changed, 0 insertions, 13 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 deleted file mode 100644 index cd679485b..000000000 --- a/doc/todo/wishlist:___96__git_annex_import__96___--_An_easy_way_to_get_data_into_an_annex.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -`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. - --- RichiH - -> [[done]] --[[Joey]] in 2012 |