Re: [Pharo-dev] inspect slices

2013-12-25 Thread Stéphane Ducasse
I would take an older image and do a merge like that you see the changes contained in the slices but this is not satisfactory. I would like to have a db storing all the changes and that we could do queries like show me the diff between the senders of foo in version 30399 and 30405 we are slowly

Re: [Pharo-dev] inspect slices

2013-12-18 Thread Nicolai Hess
2013/12/18 Marcus Denker > > On 18 Dec 2013, at 00:26, Nicolai Hess wrote: > > > How can I find out the changes from a slice that is already included > > in the main image? > > So what I just do is to “merge” —> if empty, all changes are in. > > Marcus This "all changes are in" case i

Re: [Pharo-dev] inspect slices

2013-12-17 Thread Marcus Denker
On 18 Dec 2013, at 00:26, Nicolai Hess wrote: > How can I find out the changes from a slice that is already included > in the main image? So what I just do is to “merge” —> if empty, all changes are in. Marcus

[Pharo-dev] inspect slices

2013-12-17 Thread Nicolai Hess
How can I find out the changes from a slice that is already included in the main image? For example, my current image is 30650. The slice for issue 12288 is in the main image since version 30611. I would like to see the changes from this slice for the image 30610. The issue description and the sl