Chris Muller <asqueaker at gmail.com> schrieb am Mi., 29. Jan. 2020, 03:57:

>
> It's important this feature does not get inherited by SaveDialog since the
> functionality could be harmful if used there
>

How so? What is bad about wittingly ignoring non-changes during save? You
called it pollution yourself.

It sounds like a VM-Pharo-specific process issue which may have more than
> one solution.  Or, it may be better implemented as an extension in VMMaker
> than the base tools.
>

The problem will apply to any package that is co-developped by Squeak and
Pharo guys and that is exchanged via Monticello. It cannot be solved in
VMMaker because the issue lies in Monticello or rather Pharo's shift of
tools.

The other solution I see is to auto-generate missing timestamps from the
version info in the ancestry whenever the snapshot of a version is
computed. They will only be as granular as the rate of commits of course.
And Monticello storing as it does, the operation will not be efficient in
general because you have to download all the snapshots until you find when
each method that is missing timestamps was last changed or still had a
timestamp.

Kind regards,
Jakob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20200129/350bd8d6/attachment.html>