Hi, On 2017-02-17 at 07:03 -0500 Richard Hipp <d...@sqlite.org> wrote:
>On 2/17/17, Richard Hipp <d...@sqlite.org> wrote: >> On 2/17/17, Rafal Bisingier <ra...@itec.com.pl> wrote: >>> >>> Shouldn't Fossil at least warn user trying to commit a child wit >>> timestamp earlier than parent? >> >> I think it does that, now. > >Confirmed: That fix went in 7 years ago: >https://www.fossil-scm.org/fossil/info/8fdac87b688c3ea0 It's even harder than I proposed - abort instead of warning. Thank you for confirmation. Out of curiosity: what will happen, when commited parent have timestamp far away in future? Do we have to skew our clock to commit a child? Or is there some mechanism to get around it without breaking next commit? -- Greetings Rafal Bisingier _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
