bugs/add config var preventing adjusted branch modeyohhttp://git-annex.branchable.com/bugs/add_config_var_preventing_adjusted_branch_mode/git-annexikiwiki2023-02-20T18:46:53Zcomment 1http://git-annex.branchable.com/bugs/add_config_var_preventing_adjusted_branch_mode/comment_1_d7ca1f4ccb4bc8a72788f6dcf8af9439/joey2022-05-09T15:10:38Z2022-05-09T15:00:47Z
<p>git-annex does not enter adjusted branch mode except on <code>git-annex
init</code> 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.</p>
<p>Switching back from an adjusted branch to master is a simple <code>git
checkout</code>.</p>
<p>These two facts do not argue for a separate config setting IMHO.</p>
comment 2http://git-annex.branchable.com/bugs/add_config_var_preventing_adjusted_branch_mode/comment_2_0c064717d0b85ff4b9df1bada7c6e7ad/joey2022-05-09T15:19:37Z2022-05-09T15:13:39Z
<p>It might be worth preventing <code>git-annex init</code> when in an existing, already
initalized repo from entering an adjusted branch. But re-running <code>git-annex
init</code> generally re-does initialization, except for generating a new UUID
and description. If a repo has been moved to a crippled filesystem,
I think it would be reasonable for a user to expect re-running git-annex
init will react to that. (Which can also involve setting annex.pidlock or
disabling annex.sshcaching.)</p>
comment 3http://git-annex.branchable.com/bugs/add_config_var_preventing_adjusted_branch_mode/comment_3_1f4b1f2a32f11da4c9bba95f25dd45c1/yarikoptic2023-02-17T21:50:19Z2023-02-17T21:50:19Z
here my "concern" was freeze/thawing procedure. I am yet to get to the bottom of "variance" of how differently different ACL paths behave (some exploration from this friday is <a href="https://github.com/dbic/handbook/issues/20">here</a>). And what I am afraid is that at some point, something would "trigger" git-annex to decide that path here is crippled now -- go to adjusted branches mode. If you say it cannot happen, it is ok - I will become more brave <img src="http://git-annex.branchable.com/smileys/smile4.png" alt=";-)" />
comment 4http://git-annex.branchable.com/bugs/add_config_var_preventing_adjusted_branch_mode/comment_4_0fb992fe4ef5ec14876d2d1912dca4c5/joey2023-02-20T18:46:53Z2023-02-20T18:40:00Z
<p>Well, if you unset annex.version, it will automatically reinitialize, and
would enter an adjusted branch if a crippled filesystem was detected.</p>
<p>That's the only way I can see that does not involve you running
<code>git-annex init</code> (or upgrade from v5 direct mode as mentioned earlier).</p>