From ac7a4c0f2f0e39b93322387daa19e014d9cea8ae Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Mon, 2 Dec 2019 16:48:48 +0000 Subject: [PATCH] Added a comment: dropping contents of old keys after migration --- ...comment_8_10ee2770ffe1cde367f3d310b2670539._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/git-annex-unused/comment_8_10ee2770ffe1cde367f3d310b2670539._comment diff --git a/doc/git-annex-unused/comment_8_10ee2770ffe1cde367f3d310b2670539._comment b/doc/git-annex-unused/comment_8_10ee2770ffe1cde367f3d310b2670539._comment new file mode 100644 index 0000000000..b7377c955c --- /dev/null +++ b/doc/git-annex-unused/comment_8_10ee2770ffe1cde367f3d310b2670539._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="dropping contents of old keys after migration" + date="2019-12-02T16:48:47Z" + content=""" +\"May I delete them\" -- `git-annex-drop --force` may be safer, as it also updates [[location_tracking]]. You might also want to [[git-annex-dead]] the dropped keys to prevent [[git-annex-fsck]] from complaining about lost contents. + +Re: why [[git-annex-unused]] isn't finding the unused contents, try running it with `--used-refspec=+HEAD`, and make sure `annex.used-refspec` git config is not set. Note that this will mark as unused any annexed contents not referenced from the latest tree of the HEAD branch, e.g. annexed files that were removed in some older commit. +"""]]