On Thu, 12 Feb 2015 21:17:41 +0100, Ron W <ronw.m...@gmail.com> wrote:
On Thu, Feb 12, 2015 at 2:55 PM, Warren Young <w...@etr-usa.com> wrote:
I would still prefer that Fossil self-tune, however. While it is true
that my formula doesn’t give intuitive p values, it is also true that
you
cannot pick sensible d values for a repository without knowing various
characteristics about the repository.
I think this problem is being over engineered.
The key thing is that Fossil be consistent about how many characters it
displays for a given hash. Currently, at least command is sometimes
displaying a particular has with a different number of characters than at
one other command is displaying the same hash.
I agree that this is the real problem/inconsistency to solve. after that a
fixed
prefix of reasonable length (10 or 12?) will do. as I wrote to warren I'm,
too,
not convinced that some auto-tuning would be really beneficial.
but of course the valid point remains that although
length 10 will be good for almost everybody forever, it's
not quite OK under certain circumstances such as in the netbsd example:
although hitting the
existing collisions in that repo
is on average extremely unlikely it _can_ happen to someone accidentally
interested
in one of the affected revisions quickly. at which point it would be good
if the user could
just do `fossil set prefix-length 12' thus getting rid of the collisions
and proceed. in short: an option to
customize the length might still be useful.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
