It might be worth mentioning that you can get *all* the updates applied at once by doing a "Software Update" from your current image. There's a menu item to do that, but I can't currently remember which menu it sits on. I'm sure someone else will be able to tell you. Good luck! -- Cheers, Peter. On 27 okt 2010, at 19:14, Marcus Denker <marcus.denker@inria.fr> wrote:
On Oct 27, 2010, at 5:51 PM, Tony Fleig wrote:
I am new to Pharo. This sounds like a change I would like to incorporate in my environment.
I assume 12217 is an identifier of something that might allow me to do this, but what? Is there a noob document I should have read?
12217 is the update number of version 1.2, which is the next unstable release. (To be beta end of the month).
Now if you want to cherry-pick a fix for your own development image (which I guess is based on 1.1), the other numbers are more important.
The Issues are numbers of Google bug tracker entries.
http://code.google.com/p/pharo/issues/list
(of course this just shows the open ones).
Of the three issues, just one makes sense in 1.1: 2797
http://code.google.com/p/pharo/issues/detail?id=2797
there you find the code and description of the change.
On Wed, Oct 27, 2010 at 1:28 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
Issue 3164: Fix find and seach all source Issue 1801: Rescue Sophie Undo framework Issue 2797: MIMEDocument class >> #guessTypeFromName: results in MNU
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project