From 910b9a5e4a69957b643e73da5ecc2aca3f7ac23d Mon Sep 17 00:00:00 2001 From: matrss Date: Mon, 16 Dec 2024 22:19:34 +0000 Subject: [PATCH] Added a comment --- ...t_1_828e5d92ec03594170d7ac52d346533d._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/clone_and_initialize_with_a_given_uuid/comment_1_828e5d92ec03594170d7ac52d346533d._comment diff --git a/doc/forum/clone_and_initialize_with_a_given_uuid/comment_1_828e5d92ec03594170d7ac52d346533d._comment b/doc/forum/clone_and_initialize_with_a_given_uuid/comment_1_828e5d92ec03594170d7ac52d346533d._comment new file mode 100644 index 0000000000..a00f64e35f --- /dev/null +++ b/doc/forum/clone_and_initialize_with_a_given_uuid/comment_1_828e5d92ec03594170d7ac52d346533d._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="matrss" + avatar="http://cdn.libravatar.org/avatar/cd1c0b3be1af288012e49197918395f0" + subject="comment 1" + date="2024-12-16T22:19:34Z" + content=""" +It _looks_ like you can just set annex.uuid before the first `git annex init` to achieve this: + +``` +git init / git clone +git config annex.uuid 00000000-0000-0000-0000-000000000003 +git annex init +``` + +But I would say that doing so is ill-advised. You can set a description for each repository and give the remotes descriptive names instead. If you use shared UUIDs you will run into an issue if it ever happens that two of those repositories become connected. +"""]]