On Fri, Sep 19, 2014 at 11:32 AM, kilon alios <kilon.alios@gmail.com> wrote:
I have been told that there are some problem with gitfiletree that make it not recommended for public consumption and recommendation to newcomers.

I have been using not gitfiletree but filetree alone for the past week for my project Ephestos, because I am ok commiting to git via terminal/


I have to congratulate people behind filetree it has been a smooth ride so far.I had no problems with it at all and I am using git in terminal for doing all the git commits and push etc.

filetree also has been very succesful at some major refactoring I have done to Ephestos, I had to change the name of an entire class and I had to change methods to other classes . Filetree did an excellent job not just with the export to st file but actually git was able to see which files were deleted and which were renamed.��

That meant I did not have to do any git rm .��

However I do need to git add every time I add a new method or filetree creates a new file. Usually that is not ��a problem because I can see what files are not tracked by git with git status and copy paste their paths to git add.��

So I will say overall my commits have been a process of saving in monticello , git add, git commit and git push which exactly the same process I have used for when I was and still coding in python.��

So thank you for this tool , I got fed up with the slow downs of Smalltalkhub and all its problems and it feels great to be back at using github :)��

I'd agree to that thing. Took me a while but now the Git based workflow just feels better.��
Also useful is storing snippets as gists.
Git has won, let's embrace that.
This doesn't mean that STH is not useful as a project repository. MCZs are still the main artifact.


I will keep testing for a couple a months and then completely move to github . The only thing I noticed is that sometimes monticello slows down but that may well be a problem with Pharo 4.