mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2022-05-09 11:19:34 -04:00
parent 09c94c3a96
commit 35a2f95ff9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/bugs/add_config_var_preventing_adjusted_branch_mode/comment_2_0c064717d0b85ff4b9df1bada7c6e7ad._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2022-05-09T15:13:39Z"
content="""
It might be worth preventing `git-annex init` when in an existing, already
initalized repo from entering an adjusted branch. But re-running `git-annex
init` 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.)
"""]]