Don't use date/time as ordering mechanism for checkins

[catenalogic (Geert)]

The time on my development machine is wrong (a few minutes behind). Therefore I got this history:

As you can see t he commit has an earlier date/time, but is a later commit. However, the build server sees the pull request merge as latest change (and thus builds that one instead of the latest commit). After doing a dummy (whitespace) commit with a later timestamp, everything works again as expected.

[Sparky (Dave Sparks)]

Hi Geert,

Thanks fo reporting this. This will need further investigation but we should be able to solve it either by using parent id of each commit or by creating a order number based on the log order when using topo-order option. I’ll add this our issue list.