> from pharo. Sure, it would be easier if MC and Squeaksource supported > branches, but…
The central concept of MC *is* branching and merging. In fact, with every commit you create a branch. I guess you are talking about named branches. This was broken for a while as people used dots in their initials, but Julien and I provided patches that are included in recent versions of Pharo. We use named-branches in Seaside and in various commercial projects extensively. > Another solution, for a small package like regex, would be to just > mark the latest not-pharo version, and take ownership of the project. > After all, the only non-pharo guy there is Avi. My take on this is the following: If you fork you create your own branch. It is not the job of people that fork to keep compatible with the rest of the world or to merge changes back into the main trunk. Sometimes it happens that original project merges changes from a fork, but the initiative has to come from the original maintainers. This is a good read on the topic: <http://producingoss.com/en/forks.html>. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
