Otto Behrens

> As described in this post, it seems that a reasonable compromise for dealing with Monticello metadata, is that the *.package/monticello.meta/version file be a copy of the Monticello version history...

Thanks Thierry, > Then GitFileTree has the code you need. GitFileTree recreates the complete history of the package out of the git log in a reasonable timeframe (two git queries),...

Hi Thierry, I installed Pharo 4 today and got our code loaded. Still some pain to get things going here. But I took a stab at using gitfiletree. I tried...

Oops, I created way too much ancestry; simplified a bit. On Fri, Feb 19, 2016 at 10:47 PM, Otto Behrens [email protected] wrote: > Hi Thierry, > > I installed Pharo...

Yes, the Pharo4Dev one is fine. On Fri, Feb 19, 2016 at 11:26 PM, Thierry Goubier [email protected] wrote: > Hi @ottobehrens https://github.com/ottobehrens , > > this sounds really great! I'm...

I just registered. OttoBehrens On Fri, Feb 19, 2016 at 11:35 PM, Otto Behrens [email protected] wrote: > Yes, the Pharo4Dev one is fine. > > On Fri, Feb 19, 2016...

I worked from stable. So I see lots have changed in the development branch. Looking at the merge now On Fri, Feb 19, 2016 at 11:39 PM, Otto Behrens [email protected]...

The reason why we did this was to cater for deletions / renaming / moving of classes. I suppose we could only wipe .st files. We may end up with...

Hi Dale, Have been checking out some of the stuff you've been up to. All I can say is wow, thanks. Wish I had time to help now. I've actually...

Actually, we've had trouble with the package cache. We do release branching, using the flow model (http://nvie.com/posts/a-successful-git-branching-model/). Not 100% there yet, but find that this works. Our release branch could...