On Sat, May 9, 2009 at 18:59, Stéphane Ducasse <[email protected]> wrote: > Come on this is only possible if the changes you do don't break on > other code. > else people will start to complain that we are polluting the > repository with pharo specific version.
Maybe, but I don't think so, provided it's clear the snapshots come from pharo. Sure, it would be easier if MC and Squeaksource supported branches, but… I'm just asking for some communication on what you fork, not for backporting everything to Squeak. I think at least the minimum would be to edit the project descriptions to indicate that they have a pharo branch and where to look for it. 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. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
