From 09c94c3a96b58184117da50609bd9cc06982d9b1 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 9 May 2022 11:10:35 -0400 Subject: [PATCH] comment --- ...nt_1_d7ca1f4ccb4bc8a72788f6dcf8af9439._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_1_d7ca1f4ccb4bc8a72788f6dcf8af9439._comment diff --git a/doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_1_d7ca1f4ccb4bc8a72788f6dcf8af9439._comment b/doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_1_d7ca1f4ccb4bc8a72788f6dcf8af9439._comment new file mode 100644 index 0000000000..81edca7bea --- /dev/null +++ b/doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_1_d7ca1f4ccb4bc8a72788f6dcf8af9439._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-05-09T15:00:47Z" + content=""" +git-annex does not enter adjusted branch mode except on `git-annex +init` or when you explcitly tell it to. The only exception to this that I +can find is that upgrading from a v5 repository that was in direct mode +will enter an adjusted branch. + +Switching back from an adjusted branch to master is a simple `git +checkout`. + +These two facts do not argue for a separate config setting IMHO. +"""]] -- 2.30.2