Hello !

Again I've got stuck in a dead end commit of sqlite repository https://www.sqlite.org/src/info/5774318e7329ca47 it's not the first time and I have some custom changes made to this repo, in past times I did a fresh checkout on a new folder and manually transferred my custom changes but this is not funny.

The thing happen most of the time because I do update it daily and I only noticed that I'm in a dead end commit after several days seem "changes:      None. Already up-to-date" and then I go to https://www.sqlite.org/src/timeline and see that I'm stuck in a commit tagged as "mistake" and there are several commits after that and the command "undo" do not solve the problem because there was several "updates" after the offending update/commit.

Does someone know a way to fix this issue without get into a lot of conflicts ?

Ideally I would like to "revert/undo" the offending update/commit and do an "update" command and stay in sync again without too much headache with my ongoing custom changes.


Cheers !

Hello Richard !

Thank you for reply !

Yes that did the what I was expecting, I think I remember now that I asked this before and got this answer, I searched the fossil forum for "mistake" and found nothing then came back here to ask.

Could somehow fossil detect situations like this and suggest this solution ?

Somehow based on the tag "mistake" or any other flag that could be set on a commit to allow fossil to detect this situation and give a message like:

It seems that you are in a dead state, "fossil update trunk" could fix it if you are following trunk.

Cheers !