From 318cc814b08a3f0d41e9ea9eaf3772daf13914fc Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 17 Feb 2015 17:45:24 -0400 Subject: [PATCH] comment --- ...ment_9_38f3007635b0a7b7d30bad0af8a2d0a9._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/multiple_urls_for_the_same_UUID/comment_9_38f3007635b0a7b7d30bad0af8a2d0a9._comment diff --git a/doc/forum/multiple_urls_for_the_same_UUID/comment_9_38f3007635b0a7b7d30bad0af8a2d0a9._comment b/doc/forum/multiple_urls_for_the_same_UUID/comment_9_38f3007635b0a7b7d30bad0af8a2d0a9._comment new file mode 100644 index 0000000000..5a89f6e16b --- /dev/null +++ b/doc/forum/multiple_urls_for_the_same_UUID/comment_9_38f3007635b0a7b7d30bad0af8a2d0a9._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 9""" + date="2015-02-17T21:43:16Z" + content=""" +It's entirely expected and normal for git-annex to update the UUID +of a remote with `url = somepath` when it notices that the repo at +`somepath` has changed. + +This is what you want to happen. If git-annex didn't notice and react to +the UUID change, its location tracking information (for UUID A) would be +inconsistent with the actual status of the repo (using UUID B). +"""]]