[squeak-dev] The Inbox: Monticello-eem.709.mcz
nicolas.cellier.aka.nice at gmail.com
Wed Jan 29 08:49:17 UTC 2020
Le mer. 29 janv. 2020 à 08:04, Jakob Reschke <forums.jakob at resfarm.de> a
> 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
> 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
> Hi Jakob,
however there is a quick case: if code is unchanged wrt image working copy,
then take timestamp from working copy...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev