From 1fe91705bd8052c05ca09ee3a49c29f34632d0d7 Mon Sep 17 00:00:00 2001 From: CandyAngel Date: Thu, 3 Sep 2015 08:05:52 +0000 Subject: [PATCH] Added a comment --- ...nt_3_21f51c99b1aac8b3292f60bd83493e94._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/test_whether_a_file_is_already_annexed/comment_3_21f51c99b1aac8b3292f60bd83493e94._comment diff --git a/doc/forum/test_whether_a_file_is_already_annexed/comment_3_21f51c99b1aac8b3292f60bd83493e94._comment b/doc/forum/test_whether_a_file_is_already_annexed/comment_3_21f51c99b1aac8b3292f60bd83493e94._comment new file mode 100644 index 0000000000..769c1c2b7d --- /dev/null +++ b/doc/forum/test_whether_a_file_is_already_annexed/comment_3_21f51c99b1aac8b3292f60bd83493e94._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="CandyAngel" + subject="comment 3" + date="2015-09-03T08:05:52Z" + content=""" +Hm.. having some kind of exposure of the key generation code on the command line would actually be pretty useful. So you can do something like: + + find -type f | xargs git annex genkey --format '${key} ${file}' + +Probably worth a TODO, really. + +Regarding your situation, one way of doing it would be to recursively copy the photo directory as hardlinks, `git annex import --clean-duplicates` the hardlinked copies, then diff the directories. This would give you a list of removals and those removals are already in the repo. + +Or if you just want to remove them, just run '*git annex import --clean-duplicates*' on the original photos directory. **NOTE: There was recently an issue with git-annex deleting files that it didn't have any known copies of, so a recent version is highly recommended if using --clean-duplicates.** +"""]]