Added a comment
authorgioele@678b7c03f524f2669b179b603f65352fcc16774e <gioele@web>
Sat, 1 Apr 2023 11:06:26 +0000 (11:06 +0000)
committeradmin <admin@branchable.com>
Sat, 1 Apr 2023 11:06:26 +0000 (11:06 +0000)
doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_7_f679af07b798cb4bfae75565dd46e8ed._comment [new file with mode: 0644]

diff --git a/doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_7_f679af07b798cb4bfae75565dd46e8ed._comment b/doc/bugs/Failed_adjusted_branch_update_after_error_in_drop/comment_7_f679af07b798cb4bfae75565dd46e8ed._comment
new file mode 100644 (file)
index 0000000..faff098
--- /dev/null
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="gioele@678b7c03f524f2669b179b603f65352fcc16774e"
+ nickname="gioele"
+ avatar="http://cdn.libravatar.org/avatar/366dbda84e78aff8a8a070622aeb63ce"
+ subject="comment 7"
+ date="2023-04-01T11:06:25Z"
+ 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.
+>
+>>> Weird, I don't see how a network failure could lead in that direction.
+
+All I remember is that the command that was running was `git annex sync --content`.
+
+Perhaps the fact that `annex.alwayscommit = false` was set made a difference.
+
+
+"""]]