submitted !
Yes, this has been fixed and what is shows is that the one-click build is not
On Mar 31, 2012, at 6:56 AM, Martin Sandiford wrote:
> There was a bug in timestamp handling for .changes that looks like it
> was integrated in #14410.
> http://code.google.com/p/pharo/issues/detail?id=5461
>
> Without digging further, it looks like this might be the issue with
> the two items below. �I'd try a newer image.
>
using the latest image.... I guess because it's build is not triggered automatically.
Will be fixed.
� � � �Marcus
--
Marcus Denker -- http://marcusdenker.de