Hello Fossil list,
I've noticed with some hashes when used with the "when" part of the "timeline"
command that they behave differently in some cases, which happens in the same
manner in release builds of Fossil 1.29 and 1.28. This happens the same way on
FreeBSD (ash, 1.29) and Windows (cmd.exe, 1.28).
Full timeline:
> fossil timeline -t ci -R repo1.fossil
=== 2012-08-18 ===
14:32:27 [b754381cfa] ... 3
=== 2012-08-13 ===
23:51:11 [cd12c1109d] ... 2
=== 2005-07-29 ===
12:01:00 [07004a055c] ... 1
12:00:00 [799c20dab6] initial empty check-in (user: edwardlblake tags:
trunk)
+++ no more data (4) +++
(Unexpected, it should be the same as the full timeline)
> fossil timeline after 799c20dab6 -t ci -R repo1.fossil
+++ no more data (0) +++
(Unexpected, missing [07004a055c])
> fossil timeline after 07004a055c -t ci -R repo1.fossil
=== 2012-08-18 ===
14:32:27 [b754381cfa] ... 3
=== 2012-08-13 ===
23:51:11 [cd12c1109d] ... 2
+++ no more data (2) +++
> fossil timeline after cd12c1109d -t ci -R repo1.fossil
=== 2012-08-18 ===
14:32:27 [b754381cfa] ... 3
=== 2012-08-13 ===
23:51:11 [cd12c1109d] ... 2
+++ no more data (2) +++
> fossil timeline after b754381cfa -t ci -R repo1.fossil
=== 2012-08-18 ===
14:32:27 [b754381cfa] ... 3
+++ no more data (1) +++
Shorter versions of the hash 799c20dab6 didn't change it:
> fossil timeline after 799c20 -t ci -R repo1.fossil
+++ no more data (0) +++
> fossil timeline after 799c -t ci -R repo1.fossil
+++ no more data (0) +++
"fossil info" works for both "unexpected" shorthands.
> fossil info 799c20dab6 -R repo1.fossil
uuid: 799c20dab6e868e306fa0c22d43d08cdfcf5777b 2005-07-29 12:00:00
UTC
child: 07004a055c03b1b81ca4ca9ebd064463b119b985 2005-07-29 12:01:00
UTC
leaf: no
...
> fossil info 07004a055c -R repo1.fossil
uuid: 07004a055c03b1b81ca4ca9ebd064463b119b985 2005-07-29 12:01:00
UTC
parent: 799c20dab6e868e306fa0c22d43d08cdfcf5777b 2005-07-29 12:00:00
UTC
child: cd12c1109d232980ac3fb0d70ccf9826cdde61e5 2012-08-13 23:51:11
UTC
leaf: no
...
The "repo1.fossil" repository mentioned above is available for cloning at
edwardlblake.com/projects-attic/bitsyhex/index.cgi for testing.
If it helps I've noticed that while doing some tests of the timeline command
that numbers in the "when" condition are treated differently from usual hash
strings in some cases when they're smaller than 8 characters. (It could also be
unrelated, though.)
e.g.
> fossil timeline after 1234abcd -t ci -R repo2.fossil
+++ no more data (0) +++
> fossil timeline after 10b00 -t ci -R repo2.fossil
+++ no more data (0) +++
> fossil timeline after 12345678 -t ci -R repo2.fossil
+++ no more data (0) +++
> fossil timeline after 1234567 -t ci -R repo2.fossil
=== 2013-07-05 ===
15:15:03 [ab2679f59e] Added TODO (user: edwardlblake tags: trunk)
=== 2012-10-09 ===
23:47:01 [c1ef0da875] files (user: edwardlblake tags: trunk)
23:39:51 [476f6f3d00] initial empty check-in (user: edwardlblake tags:
trunk)
+++ no more data (3) +++
> fossil timeline after 1000 -t ci -R repo2.fossil
=== 2013-07-05 ===
15:15:03 [ab2679f59e] Added TODO (user: edwardlblake tags: trunk)
=== 2012-10-09 ===
23:47:01 [c1ef0da875] files (user: edwardlblake tags: trunk)
23:39:51 [476f6f3d00] initial empty check-in (user: edwardlblake tags:
trunk)
+++ no more data (3) +++
A quick perusal in the mailing list archives through Google I found a thread
that might be referring to the same issue:
https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg08333.html
Thanks,
Edward Blake
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
