Re: [fossil-users] Sixteen-digit event IDs
2014-06-30 17:12 GMT+02:00 Stephan Beal: i like it, but how about %U (big U, for UUID)? That one is still available. Or maybe %H (hash). Ah, now i see that %S could mean SHA1, so now %S makes more sense to me. %S stands for STRINGID already, I see no reason to change it. http://fossil-scm.org/index.html/artifact/49a234dc?ln=56 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
Re: [fossil-users] Sixteen-digit event IDs
On Wed, Jul 2, 2014 at 9:59 AM, Jan Nijtmans jan.nijtm...@gmail.com wrote: %S stands for STRINGID already, I see no reason to change it. http://fossil-scm.org/index.html/artifact/49a234dc?ln=56 Indeed. i overlooked that. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Sixteen-digit event IDs
On Jun 30, 2014 2:20 AM, Jan Nijtmans jan.nijtm...@gmail.com wrote: 2014-06-27 23:40 GMT+02:00 Andy Goth andrew.m.g...@gmail.com: How come events are always shown with (at least) sixteen digits on the timeline whereas other artifacts are given ten digits? http://www.fossil-scm.org/fossil/timeline?n=20y=e Just because it was implemented that way originally ;-) I would like to propose to use the same algorithm as in other places: Make sure that the displayed UUID contains at least one lowercase ASCII, with a minimum of length 10. This code isn't an area of expertise of mine, but isn't the one lower case ASCII requirement hopeful? The hyperlink uses the full UUID. The %S formatter could be used for the display part: http://fossil-scm.org/index.html/info/734d429940 To me the result looks good, but I would appreciate a second opinion before merging this to trunk. Any objections? Is there any place in the UI where changing the default length of %S causes a possible incompatibility. (If so, using the %.16s format would be more logical anyway.) 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Sixteen-digit event IDs
2014-06-27 23:40 GMT+02:00 Andy Goth andrew.m.g...@gmail.com: How come events are always shown with (at least) sixteen digits on the timeline whereas other artifacts are given ten digits? http://www.fossil-scm.org/fossil/timeline?n=20y=e Just because it was implemented that way originally ;-) I would like to propose to use the same algorithm as in other places: Make sure that the displayed UUID contains at least one lowercase ASCII, with a minimum of length 10. The hyperlink uses the full UUID. The %S formatter could be used for the display part: http://fossil-scm.org/index.html/info/734d429940 To me the result looks good, but I would appreciate a second opinion before merging this to trunk. Any objections? Is there any place in the UI where changing the default length of %S causes a possible incompatibility. (If so, using the %.16s format would be more logical anyway.) 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
Re: [fossil-users] Sixteen-digit event IDs
On Mon, Jun 30, 2014 at 11:20 AM, Jan Nijtmans jan.nijtm...@gmail.com wrote: The %S formatter could be used for the display part: http://fossil-scm.org/index.html/info/734d429940 i like it, but how about %U (big U, for UUID)? That one is still available. Or maybe %H (hash). Ah, now i see that %S could mean SHA1, so now %S makes more sense to me. -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do. -- Bigby Wolf ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Sixteen-digit event IDs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How come events are always shown with (at least) sixteen digits on the timeline whereas other artifacts are given ten digits? http://www.fossil-scm.org/fossil/timeline?n=20y=e - -- Andy Goth | andrew.m.goth/at/gmail/dot/com -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTreTRAAoJELtYwrrr47Y4090IAIgVQ/T1S9usyvEGZ4309c6d IQoD2TK9kgm7TDH1QPT1lurQwcugq1A7Q8PbR5ETedvIfGuQGRauajpSsbw1RU1/ rKcZQ/aCRMZUz5EP46CaCuw5vKI8zOa3aqIGzmQPYoqx1nVanoKe8JO6b0larbSS SKo1DBA5NAPjYZqbRMX7Wp9Ypn5YcWS1PxwBGY6GNpEcYwycv0D15PCHLd8JwjVd mVM4F6rbsyE9gjs5yjG5b0ZCfmx2HJqQWP0Z28FVaB40CexSzCOnbMe2zdmHrj57 dZlK6AKE0JHm2KRf7zzyezMC8chEXFBYi5rhLFxxYkwf/PX+ey2tDcAYzSYgJPY= =hmbi -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Sixteen-digit event IDs
Thus said Andy Goth on Fri, 27 Jun 2014 16:40:33 -0500: How come events are always shown with (at least) sixteen digits on the timeline whereas other artifacts are given ten digits? Perhaps because prior to [49467d2a494] short events that collided with other types of artifacts were silently hidden so to avoid this 16 digits were chosen? Just a guess... http://www.fossil-scm.org/index.html/info/49467d2a494aae8b65e6ec8d118cb4fb0fe080c1 Andy -- TAI64 timestamp: 400053ade9a3 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
