[Pharo-project] Thoughts on Monticello/GIT?
chaetal at gmail.com
Fri Oct 29 10:03:24 EDT 2010
Smalltalk code is objects, not text. So I'm for exploration and development
of this (traditional Smalltalk Envy, Store, Monticello...) direction instead
of trading Smalltalk benefits for cheap popularity :) But these alternatives
don't interfere I guess.
2010/10/29 Geert Claes <geert.wl.claes at gmail.com>
> A feedback post on the ESUG list from the GSoC somehow turned into an idea
> sandpit. I would like to test the water about one of the ideas to get a
> feeling about what people thoughts are regarding Pharo/GIT? Some
> has already been done via the gitocello (I like the name) project.
> Paolo Bonzini-2 wrote:
> > ... For the VCS, I've always been surprised there's no git or svn backend
> > for Monticello. It wouldn't seem _too_ hard to have a directory per
> > package and replace each .mcz file with a commit in that directory.
> > Alternatively, there's actually very little GST-specific code in
> > http://github.com/timfel/gitocello (a Squeak+Monticello <-> GST+git
> > bridge), so if someone wants to play with it...
> View this message in context:
> Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev