We have been experiencing issues with empty mcz versions recently.
Will this make that problem more invisible?

On Sun, Nov 30, 2014 at 1:52 PM,  <commits at source.squeak.org> wrote:
> David T. Lewis uploaded a new version of Monticello to project The Trunk:
> http://source.squeak.org/trunk/Monticello-dtl.605.mcz
>
> ==================== Summary ====================
>
> Name: Monticello-dtl.605
> Author: dtl
> Time: 30 November 2014, 2:51:55.03 pm
> UUID: 7ee2c5c7-7da0-4241-bf1d-148741ed76a2
> Ancestors: Monticello-bf.604
>
> Add a nil check, allows saving an initial empty package in a new repository.
>
> =============== Diff against Monticello-bf.604 ===============
>
> Item was changed:
>   ----- Method: MCWorkingCopy>>newVersion (in category 'operations') -----
>   newVersion
>         | packageSnapshot parentSnapshot patch patchBlock |
>         parentSnapshot := self parentSnapshot.
>         patchBlock :=  [patch := (packageSnapshot := package snapshot) patchRelativeToBase: parentSnapshot].
>         patchBlock value. "Ensure that this is called at least once."
>         ^ (self requestVersionNameAndMessageWithSuggestion: self uniqueVersionName
>                 initialMessage: self patchMessageSuggestion
>                 patchBlock: patchBlock
>         ) ifNotNil: [:tuple |
>                 self newVersionWithName: tuple first withBlanksTrimmed
>                         message: (self patchMessageStripped: tuple second)
> +                       snapshot: ((tuple size >= 3 and: [tuple third notNil and: [tuple third notEmpty]])
> -                       snapshot: ((tuple size >= 3 and: [tuple third notEmpty])
>                                 ifTrue: [       MCPatcher apply: (patch ignoring: tuple third) to: parentSnapshot]
>                                 ifFalse: [packageSnapshot])]!
>
>