Thanks for all the answers. I used Mariano's way, but I'd like to learn to do this monticello.

Stephane, I didn't understand the method you proposed. Anyway, there are two problems that I need to solve:

a) I don't wan't to include everything I changed from the package. There are some things that I changed for debugging. So, I can't fileout everything and I don't know if monticello will let me do what I want.

b) Supose the change includes 3 separate packages, that should be seen as a one. Loading only one package only would break things, so I'd like the change to include all 3 in one operation.

Can this be done?

On Fri, Aug 14, 2009 at 7:44 PM, St��phane Ducasse <stephane.ducasse@inria.fr> wrote:
save your package with monticello.
Create a package empty call sliceXXX and add the dirty package as
dependent (one click button)
and publish it.
MC has good supprt for merging.


On Aug 14, 2009, at 4:08 PM, Javier Pim��s wrote:

> It seems fixing bugs is not the only hard part... I've a bunch of
> fixes for GLCanvas, and a small proposed change for the class
> browser but I can't find a way to export a diff of all the changed
> packages, nor a diff of an entire package nor a diff of a class so
> anybody can see the changes before commiting... Do I have to file
> out every class I changed? there has to some easier way.
>
> Thanks,
> �� �� �� �� �� ��Javier.
>
> --
> Javier Pim��s
> Ciudad de Buenos Aires
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



--
Javier Pim��s
Ciudad de Buenos Aires