[Seaside] greaseString on ScaledDecimal

Dale Henrichs dale.henrichs at gemtalksystems.com
Tue Jun 16 09:17:28 UTC 2015


Johan,

I think a better solution would be to merge the changes for 
SeasideSt/Grease into GsDevKit/Grease ... then move the GsDevKit/Grease 
project to SeasideSt/Grease, then fork SeasideSt/Grease on GsDevKit ....

This would avoid any conflicts for the GsDevKit/Grease users and then 
make the SeasideSt/Grease project the master project ...

We did a similar move when we moved projecs from glassdb to GsDevKit ...

Presumably there aren't a lot of SeasideSt/Grease users at the moment?

Dale

On 6/15/15 11:47 AM, Dale Henrichs wrote:
> There is probably a way to merge the commits between the two repos and 
> let the SeasideSt/Grease project take precedence  ...
>
> Dale
>
> On 06/15/2015 11:17 AM, Johan Brichau wrote:
>>
>>> On 15 Jun 2015, at 20:13, Dale Henrichs 
>>> <dale.henrichs at gemtalksystems.com 
>>> <mailto:dale.henrichs at gemtalksystems.com>> wrote:
>>>
>>> Are there differences between the two in terms of 
>>> packaging/structure? Or is mainly the comit stream that you are 
>>> thinking of?
>>
>> The commit stream and the Metacello load conflicts for everyone.
>> There are no package differences (at least there should not be any) 
>> as the repositories for Grease are all the same. However, manually 
>> keeping track of changes to both the Smalltalkhub repo and the 
>> GsDevKit one, is not an option in the long run either.
>>
>> Johan
>>
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20150616/859ca1b9/attachment.htm


More information about the seaside mailing list