On Wed, Feb 1, 2012 at 4:42 AM, Leo Razoumov <slonik...@gmail.com> wrote:
> I am reading "Fossil File Formats" at > http://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki > where it says (section on Control Artifacts): > > "When two or more tags with the same name are applied to the same > artifact, > the tag with the latest (most recent) date is used." > > Most recent date according to what clock? Fossil is distributed and > clocks on different machines can be out of sync with each other so are > artifact's timestamps. Can it cause problems? Am I missing something? > Internally fossil uses a mix of Unix timestamps and (mostly, AFAIK) Julian dates. Unix timestamps are GMT/UTC and Julian is, as far as i'm aware, also timezone-independent. (Maybe someone better-versed in time handling can correct my Julian understanding.) http://en.wikipedia.org/wiki/Julian_day Commits/changes are performed on the client (then synched to the server), which implies that the timestamps are local and that a clock drift on a local machine will result in funky data on the server. (But again, perhaps someone here can correct that assumption.) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
