The documented format is:
Timestampstrings can be of the form: <authorname><date><time>. <authorname><date> <date><time> <date><time><authorname> <date><authorname> <historical>
Says /who/? When I created all these timestamps to document a refactoring change there was no documented restriction on timestamps I could see. Why impose restrictions which have little value? Why needlessly break compatibility? That timestamp *contains useful information*. Why ban it?
If you *want* VMMaker to load in Pharo you need to ensure that Pharo supports the timestamps *that exist* not the timestamps you want to impose on the community.
Eliot we do not impose anything to the community. Please do not bash us we have enough to do without that! Apparently the code was like that and people (may be johan) started to make sense out of it. Stef