There are two cases: (1) SHA1 prefixes for human-consumption (2) SHA1 prefixes as part of URLs
What do people think would be a good default length for each case? Jan prefers the full 40-characters for (2) and went to a lot of trouble to change that at one point . But I find those 40-character long URL parameters annoying a have been slowing reducing the length of (2) in specific places where it annoys me. I propose either 16 or 20 as the default length for (2). Probably the shorter. The default length of (1) has traditionally be 10 characters, though as J notes, that is sometimes extended in order to find a character in the range of [a-f]. There are historical reasons for that extension - reasons which have now expired. And so I'm am ok with making the length of (1) the same in all cases. A value of 10 or 12 seems like a reasonable default to me. The prefix lengths can set in a single place in the code (https://www.fossil-scm.org/fossil/info/98dae687a6c7858?ln=625-630) so that the default length decisions can easily be revisited later, and/or changed at compile-time or at run-time. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
