Added a comment
This commit is contained in:
parent
71e0ec2901
commit
170c5edb44
1 changed files with 19 additions and 0 deletions
|
@ -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.
|
||||||
|
|
||||||
|
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue