From f9789e421c587f37535c999f3876eb083656d64e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 14 Mar 2017 19:45:28 -0400 Subject: comment --- .../comment_5_e887b2d2ecbce3de22c517afd500e783._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/tips/recover_data_from_lost+found/comment_5_e887b2d2ecbce3de22c517afd500e783._comment (limited to 'doc/tips') diff --git a/doc/tips/recover_data_from_lost+found/comment_5_e887b2d2ecbce3de22c517afd500e783._comment b/doc/tips/recover_data_from_lost+found/comment_5_e887b2d2ecbce3de22c517afd500e783._comment new file mode 100644 index 000000000..125b47083 --- /dev/null +++ b/doc/tips/recover_data_from_lost+found/comment_5_e887b2d2ecbce3de22c517afd500e783._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2017-03-14T23:40:45Z" + content=""" +If you're worried about lost+found containing non-annexed content, you can +copy (`cp`) the files, rather than moving them (`mv`). After adding the +files, `git annex unused` will find any non-annexed ones that were added, +and they can then be removed. + +This tip was written before `git annex reinject --known` existed, but that +is also a good way to do it. +"""]] -- cgit v1.2.3