From 7ea8411cfb039292233b56a8a3c9c5de5adc89f3 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 27 Jul 2020 11:40:30 -0400 Subject: [PATCH] comment --- ...omment_3_00418ada32a4d93dfd3334686e391a23._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/best_way_to_move_a_git_annex_repo_trought_file_system/comment_3_00418ada32a4d93dfd3334686e391a23._comment diff --git a/doc/forum/best_way_to_move_a_git_annex_repo_trought_file_system/comment_3_00418ada32a4d93dfd3334686e391a23._comment b/doc/forum/best_way_to_move_a_git_annex_repo_trought_file_system/comment_3_00418ada32a4d93dfd3334686e391a23._comment new file mode 100644 index 0000000000..ac33c4c176 --- /dev/null +++ b/doc/forum/best_way_to_move_a_git_annex_repo_trought_file_system/comment_3_00418ada32a4d93dfd3334686e391a23._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2020-07-27T15:38:22Z" + content=""" +Yeah, this is not really a problem. Do note that, when a git-annex repo is +moved to a new drive, this does change some of the internal details that +git-annex keeps track of (inode numbers). If the repository has unlocked +files in it, this can make git-annex's handling of those a little slow at +first, until it learns the new details. +"""]]