[Pharo-project] Latest changes in FS
Hi Camillo, Thanks for the updates on FS :) It seems that you did not based FS-Core from Sean's latest version which introduce 'moveTo:'. Is there a reason ? To be honest, I'm a bit lost between the different versions of FS. Thanks ! Francois
oh my bad... I am so used to git that I constantly forget to update and merge remote changes first... will update the config, thanks for the remark :) On 2012-01-20, at 21:54, Francois Stephany wrote:
Hi Camillo,
Thanks for the updates on FS :) It seems that you did not based FS-Core from Sean's latest version which introduce 'moveTo:'. Is there a reason ?
To be honest, I'm a bit lost between the different versions of FS.
Thanks !
Francois
On 1/22/2012 7:28 AM, Camillo Bruni wrote:
oh my bad...
I am so used to git that I constantly forget to update and merge remote changes first...
will update the config, thanks for the remark :)
Hello, I am not used to git, so I do not understand what git does for you that Monticello/Metacello or whatever do not. I have only used it for personal projects or to clone from github. Is there a feature request here? Something that would improve your workflow? If so, could you describe it. You are probably not alone in your experience or desire. Just curious. Thanks. Jimmie
On 2012-01-22, at 16:14, Jimmie Houchin wrote:
On 1/22/2012 7:28 AM, Camillo Bruni wrote:
oh my bad...
I am so used to git that I constantly forget to update and merge remote changes first...
will update the config, thanks for the remark :)
Hello,
I am not used to git, so I do not understand what git does for you that Monticello/Metacello or whatever do not. I have only used it for personal projects or to clone from github.
Is there a feature request here? Something that would improve your workflow? If so, could you describe it. You are probably not alone in your experience or desire.
Hi Jimmie, Monticello: - MC automatically creates a new "branch" if you commit unmerged changes - Branches are not clearly visible in the GUI, though clearly present in the model What git does: - unmerged changes get rejected (unless forced) [svn did the same here] - clear notion of branches and versions (not based on the name of the commit) I could list some more shortcomings of MC, though as above they key issue is not the MC model but rather the GUI built around it :) best cami
participants (3)
-
Camillo Bruni -
Francois Stephany -
Jimmie Houchin