On 7/11/17, Martin Vahi wrote:
>
> it would be nice, if the
> Fossil were able to recover from that kind of situations
> itself, automatically.
Fossil *does* recover from situations like this automatically
In this case, I don't think the prior fossil command was killed
unexpectedly. Instead
I do not know the exact operation that I killed by
the key combination Ctrl-C, but the operation was probably
one of the following:
fossil addremove
or
fossil commit
or
fossil pull
or
fossil push
The result is a "corrupted" repository file with a
"locked SQLite" database file.
I
2 matches
Mail list logo
