From 54a0db25637962dfce5188646565a431d9fd52cb Mon Sep 17 00:00:00 2001 From: kyle Date: Wed, 21 Apr 2021 16:32:42 +0000 Subject: [PATCH] Added a comment: re: Are my unlocked, annexed files still safe? --- ...10_1f5ca7ccd35e9b102bf24b3f14deeee1._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/git-annex-unlock/comment_10_1f5ca7ccd35e9b102bf24b3f14deeee1._comment diff --git a/doc/git-annex-unlock/comment_10_1f5ca7ccd35e9b102bf24b3f14deeee1._comment b/doc/git-annex-unlock/comment_10_1f5ca7ccd35e9b102bf24b3f14deeee1._comment new file mode 100644 index 0000000000..8ef849a9f4 --- /dev/null +++ b/doc/git-annex-unlock/comment_10_1f5ca7ccd35e9b102bf24b3f14deeee1._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="kyle" + avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3" + subject="re: Are my unlocked, annexed files still safe?" + date="2021-04-21T16:32:42Z" + content=""" +@pat: +> Basically, unlock gives me an editable copy of the file - but I always +> have the original version, and can revert or check it out if I need +> to. Is that correct? + +Yes, it's a copy as long as you don't set `annex.thin=true` (as you +mention). Just as with locked files, though, you may not be able to +get the content back from an earlier version if you've dropped unused +content. + +"""]]