From fb93fbc564171c5ff6251eac0c44443fe830afa0 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 10 Feb 2023 14:16:23 -0400 Subject: [PATCH] comment --- ...t_2_149502c4d8fa2c50507e7e6e312f9703._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/adjusted__47__main__40__unlocked__41___not_syncing_with_main/comment_2_149502c4d8fa2c50507e7e6e312f9703._comment diff --git a/doc/bugs/adjusted__47__main__40__unlocked__41___not_syncing_with_main/comment_2_149502c4d8fa2c50507e7e6e312f9703._comment b/doc/bugs/adjusted__47__main__40__unlocked__41___not_syncing_with_main/comment_2_149502c4d8fa2c50507e7e6e312f9703._comment new file mode 100644 index 0000000000..4c3f9e3866 --- /dev/null +++ b/doc/bugs/adjusted__47__main__40__unlocked__41___not_syncing_with_main/comment_2_149502c4d8fa2c50507e7e6e312f9703._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2023-02-10T18:07:47Z" + content=""" +For an adjusted branch, git-annex keeps +a hidden ref, `refs/basis/adjusted/master(unlocked)`. +That ref also needs to be renamed if you're going to +rename the adjusted branch and the original branch. + +It's of course fine to delete the old adjusted branch and +re-adjust the new branch. + +I think that git-annex should warn if it cannot find +the basis ref for an adjusted branch. +"""]] -- 2.30.2