Thank you again for the answer ! Now I understand the problem, maybe fossil could give an extra bit of info when it's invoked like "fossil update" maybe something like:
You are now at "branch_name" and it's behind "trunk" by X commits. ? > Tue Feb 09 2016 6:46:13 pm CET CET from "Richard Hipp" <drh at sqlite.org> > >>Thanks for the answer ! >> >> Although it seems a bit weird this behavior of get stuck on one specific >> branch. >> > The check-in you were stuck on was originally on trunk. But when an > error was discovered in that check-in, it was diverted to a branch. > You rode the diversion onto the branch. > > ?
