On 1/16/18, Martin Gagnon <[email protected]> wrote:
> Hi,
>
> Few minutes ago, I've commit a small fix on trunk and my commit has
> create a fork. I thought that since a while, fossil will not allow
> forking unless "--allow-fork" is specified, which I didn't specify. Is
> it normal, or is it an uncovered corner case ?

There are unresolvable race conditions in the anti-fork checking.
"Unresolvable" in the sense that the only fix is to introduce some
kind of locking on the server, which we definitely do not want to do.

It is easy enough to recover from the occasional fork that happens due
to a race.

-- 
D. Richard Hipp
[email protected]
_______________________________________________
fossil-dev mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to