$ ./fossil timeline -t e
=== 2013-08-26 ===
07:35:00 [94694585cd]
=== 2011-04-27 ===
02:15:00 [22c9d9a61f] <b>Design Note:</b> About the "Irreversible
Schema Change" (user: drh)
=== 2010-11-01 ===
17:24:02 [60c7229505] Release Notes (user: drh tags: release)
=== 2010-10-09 ===
10:26:44 [dfd6e05ab2] <b>Design Note:</b> Scaling Fossil Up (user:
drh tags: blog)
=== 2010-10-05 ===
03:55:50 [82cdfeeffe] Release 2010-10-05 03:55:49 (user: drh tags: release)
+++ no more data (5) +++
Compare this with the uuid's in the following web-page:
<http://fossil-scm.org/index.html/timeline?y=e>
The UUID's are different! It looks like the web-page is correct, the
UUID's in the "fossil timeline" output are the UUID's of the
corresponding manifest corresponding with the event. This
happens for event UUID's only, other UUID's don't have
this problem (that's probably why no-one noticed this before)
Regards,
Jan Nijtmans
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
