Thanks Marcus. By reading the issue 2797, I can see what changes I need to make. I'm guessing there is no automated way to do this?
TF On Wed, Oct 27, 2010 at 10:14 AM, Marcus Denker <[email protected]>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 <[email protected]> > 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 > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
