Thanks

-----

As stated in the wiki http://www.fossil-scm.org/index.html/doc/tip/www/reference.wiki:

A version in fossil is 40 character hexadecimal string. fossil will be able to figure out which version you want with any prefix of that string that is distinct from all others. Commands which require a version are looking for that string, the unique prefix, or a tag.

kkinnell added on 2009-01-05 15:41:04:
A bit off-ticket-topic, but just to clarify some points about the cli docs here:

The cli reference doc is incorrect as of 2009-01-05, and will be amended in the next version. I will push the newer doc as soon as I am able to do so.

In fact, there is a minimum prefix length of four characters for "versions" (see the concepts page, section 2.1 Identification of Artifacts, paragraph 3 beginning "When referring"...)

Also, "version" is a bit of a misnomer, what we're actually dealing with are Artifact IDs, which happen to be 160 bit SHA1 hash digests of n-length bit sequences (which is the basic thrust of the cited section.)

And now, back to the actual feature request ...

anonymous added on 2009-01-06 10:28:45:
kkinnell - I note your point about version/artifact ID. I'll try to use the right designation in future.

To clarify I'm requesting to control the shorthand length artifact IDs displayed as links on the webpage rather than the stored artifact IDs (40 chars).

i.e the 263b45306c rather than the 263b45306ce3fbc7f93e3f3be170f550aa8104c5

If a minimum of 4 chars is required, so be it. 4 chars is easier on the eye than 10 chars.

One of the implementation issues I can foresee is the likelihood of ambiguity in fossil as the number of characters displayed is reduced. I believe it would be satisfactory when fossil comes across an ambiguity situation it just returns an error stated a message to that effect on the cli and on the website suggest changing the configuration to increase the number of chars display.