From aee5e0c6fc3c72a950da1ca5e2e605ace0650da5 Mon Sep 17 00:00:00 2001 From: jgoerzen Date: Sat, 10 Sep 2022 00:32:57 +0000 Subject: [PATCH] Added a comment --- .../comment_2_07861ab33ec31659ec3cfa8520580fd4._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__/comment_2_07861ab33ec31659ec3cfa8520580fd4._comment diff --git a/doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__/comment_2_07861ab33ec31659ec3cfa8520580fd4._comment b/doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__/comment_2_07861ab33ec31659ec3cfa8520580fd4._comment new file mode 100644 index 0000000000..4fd8f9fdde --- /dev/null +++ b/doc/forum/Unlocked_mode_without_data_also_under_.git__47__annex__63__/comment_2_07861ab33ec31659ec3cfa8520580fd4._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="jgoerzen" + avatar="http://cdn.libravatar.org/avatar/090740822c9dcdb39ffe506b890981b4" + subject="comment 2" + date="2022-09-10T00:32:57Z" + content=""" +In my case, I really don't care about losing the old version of a file. I have ZFS snapshots and backups to take care of that. I do use thin, and that particular issue doesn't really bother me. I wounder if a \"superthin\" where there is no hardlinking into .git/annex at all would be possible? I'm aware that, yes, that could make previous versions unavailable and so forth. +"""]]