[squeak-dev] Re: Squeak 5.0 Strange Commit Behavior

David T. Lewis lewis at mail.msen.com
Tue Nov 3 13:11:34 UTC 2015


On Tue, Nov 03, 2015 at 01:34:15AM -0800, marcel.taeumel wrote:
> Hi Chris,
> 
> it seems that Kernel-cmm.937 and System-cmm.756 are "broken". The diff from
> my changes to Kernel-cmm.936 and System-cmm.755, which are the previous
> versions, looks fine.
> 
> Considering that MCZs save the full snapshot anyway ... should I just
> commit? =)

I expect you can commit without problems. To be extra safe, you can commit
to your own package-cache, then copy the result from package-cache to trunk
if you are happy with the result.

Dave




> 
> The Tools-cmm.629 looks fine and diffs fine.
> 
> I touched all packages with this code:
> 
> repo := MCRepositoryGroup default repositories detect: [:repo | repo
> description endsWith: 'squeak50'].
> 
> PackageOrganizer default packages do: [:pkg |
>   [(pkg mcPackage workingCopy changesRelativeToRepository: repo)
>     isEmpty ifFalse: [pkg mcPackage workingCopy modified: true]]
>       on: Warning do: [:warning | 
>         Transcript showln: pkg name; showln: warning messageText.
>         warning resume]].
> 
> This is what I got:
> 
> <http://forum.world.st/file/n4859057/squeak-50-empty-mcz.png> 
> 
> Best,
> Marcel
> 
> 
> 
> --
> View this message in context: http://forum.world.st/Squeak-5-0-Strange-Commit-Behavior-tp4858951p4859057.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.


More information about the Squeak-dev mailing list