Hi On Thu, 16 Feb 2017 at 14:15 -0800 Ross Berteig <r...@cheshireeng.com> wrote:
> Sure, we'd all love it if everyone kept their clocks in sync, but in the real > world skew is simply going to happen. In the absence of a central server to > provide the authoritative time stamp, a DVCS like both Fossil and Git has no > real choice other than to trust the time provided by each local machine as > authoritative enough to document each commit. > > If commits from each user of a project end up lined up in order on the > timeline, that is just a happy side effect of people keeping their clocks > synchronized. > > Having a parent committed after a child does look odd, but I think it has to > be simply accepted as part of the record, warts and all, of the work on the > project. Shouldn't Fossil at least warn user trying to commit a child wit timestamp earlier than parent? I suppose that in the moment of commit fossil is able to check this two timestamps (system time and ts of parent checkin) and compare it? I'd even say that in case of local time misconfiguration (when commiting child will end up with earlier timestamp than it's parent) it's possible to semi-automagically "fix" this by setting "computed timestamp" a the new commit timestamp. or better by simply executing what "fossil amend --date" do. -- 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
