On 22 July 2014 11:48, Stephan Beal <[email protected]> wrote: > On Tue, Jul 22, 2014 at 11:35 AM, Michai Ramakers <[email protected]> > wrote: >> >> (FWIW, I know there have been flaws in this area before, and although >> I am not a dev having/willing to deal with them, I agree with Jan that > > AFAIR i reverted that to not be the default behaviour (IMO it should not be > because it's a long-standing historical behaviour and we don't fully know > the implications of removing it).
right, I remember, but I think for the purpose of weeding out bugs there, it became default again: http://fossil-scm.org/index.html/info/8364065c45ec839d01e0a0535ebd754f81e9cac4 >> ... "fossil undo" is available to undo changes to the working checkout. >> /tmp/f/a$ f tim >> === 2014-07-22 === >> 09:22:41 [4b720ef551] *CURRENT* test (user: michai tags: trunk) >> === 2014-01-01 === >> 00:00:00 [b58cc4d981] initial empty check-in (user: michai tags: trunk) >> +++ no more data (2) +++ > > (That last line is a little confusing, IMO. Almost looks like an error.) the '00:00:00'? That's because of the 'fossil new --date-override 2014-01-01' (e.g. fake initial commit well in the past). Michai _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
