[Pharo-users] How to contribute to Pharo Launcher?

Tim Mackinnon tim at testit.works
Mon Jun 18 12:35:59 EDT 2018


Ok - I’ve done a save for both packages - hopefully they are useful:

Name: PharoLauncher-Spec-TimM.70
Author: TimM
Time: 18 June 2018, 5:32:00.928101 pm
UUID: 5e888bd7-4e2b-0d00-85bb-537409965ccd
Ancestors: PharoLauncher-Spec-TimM.69


Name: PharoLauncher-Core-TimM.172
Author: TimM
Time: 18 June 2018, 5:34:46.055084 pm
UUID: 6a2b63e1-4e2b-0d00-85bc-0fed09965ccd
Ancestors: PharoLauncher-Core-TimM.171



> On 18 Jun 2018, at 16:30, Cyril Ferlicot D. <cyril.ferlicot at gmail.com> wrote:
> 
> On 18/06/2018 17:27, Tim Mackinnon wrote:
>> Hi Cyril - I have to confess that I don’t recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasn’t that a Pharo core thing?
>> 
>> I get the impression that I don’t just press save on each package against sthub do I?
>> 
>> Sorry to be so dumb - I’ve just swapped out Monticello usage for Git usage these days.  Just need a few hints to get back on track
>> 
> 
> You need to save the two packages individually.
> 
> While git is project oriented, StHub is package oriented.
> 
> Slices are only for Pharo development. (One could adapt them to make
> Monticello more project oriented but it is currently not the case).
> 
> So in conclusion, yes you need to press save on each package. :)
> 
>> Tim
>> 
>> 
>> 
> 
> 
> -- 
> Cyril Ferlicot
> https://ferlicot.fr
> 




More information about the Pharo-users mailing list