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

Added a comment

Browse source
This commit is contained in:
gioele@678b7c03f524f2669b179b603f65352fcc16774e 2023-03-25 08:47:01 +00:00 • committed by admin
parent 02fe361055
commit 4d198a6665
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_5_7b989f777b211f21ca0e9ca681869bff._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="gioele@678b7c03f524f2669b179b603f65352fcc16774e"
nickname="gioele"
avatar="http://cdn.libravatar.org/avatar/366dbda84e78aff8a8a070622aeb63ce"
subject="comment 5"
date="2023-03-25T08:47:01Z"
content="""
> I wonder if there are other situations where modifications can prevent checkout of the updated adjusted branch?
I clearly remember seeing something similar when a `sync` failed due a non-recoverable network failure. Unfortunately I have no logs from that day.
> It seems wise for git-annex to defend against it in depth, by making sure no crash can leave it in detached head state.
Perhaps also extend `fsck` to automatically recover from such a state? Or at least suggest a couple of possible solutions to the user?
"""]]