mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
CandyAngel 2018-07-05 13:53:47 +00:00 committed by admin
parent fb730c3731
commit f60e0df0e0
1 changed files with 14 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
doc/bugs/Importing__95__Commands__95__Destructive__95__by__95__default/comment_1_96fae5927db6badfe13466cd27cfc371._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="CandyAngel"
avatar="http://cdn.libravatar.org/avatar/15c0aade8bec5bf004f939dd73cf9ed8"
subject="comment 1"
date="2018-07-05T13:53:46Z"
content="""
This shouldn't be under bugs, it is the intended behaviour.
Both the words `import` and `reinject` relate to the movement of something from one place to another (importing goods, injecting fluids). Descriptions for both these commands state that data will be *moved* into the annex in the first sentence. If you aren't reading docs before using these commands, better docs are hardly going to have helped..
What you are trying to do can be done with `import --skip-duplicates` then `cp` -> `reinject`, albeit a bit of a pain. Personally, I would use `calckey` to generate the hashes (and keep them in a file), add hashes for files not listed in that file, then use that file to find out what keys were unknown and `import --duplicate` just those files.
..or [following a suggestion I made a while ago](http://git-annex.branchable.com/todo/Alternative_mode_control_for_import/) `git annex import --mode=Di,Nsi` would do what you want (injects duplicates without deleting, adds new without deleting) :P
"""]]