he means in which tracker does he put the issue, so it can be integrated, I suppose.
if is that, is in cog tracker: http://code.google.com/p/cog/issues/list Esteban On Nov 9, 2012, at 10:50 AM, Igor Stasenko <[email protected]> wrote: > On 8 November 2012 14:16, Stefan Marr <[email protected]> wrote: >> Hi: >> >> On 06 Nov 2012, at 17:59, Stéphane Ducasse wrote: >> >>>> The attached change set fixes bit rot in the StackInterpreterSimulator and >>>> related classes. >>>> >>>> Here a brief summary: >>>> >>>> - VMClass>>#doOrDefer: now uses ProcessBrowser>>#isUIProcess: instead of >>>> Project >>>> - it replaces the use of #asDisplayText with StringMorph>>#contents:. >>>> - use of ThreadStream>>#on: is replaced with ThreadSafeTranscript>>#new >>>> - Utilities is replaced by UIManager>>#default >>>> - and #primitiveGetAttribute now uses the non-depricated `Smalltalk vm >>>> getSystemAttribute: attr` >> >> Here are more complete patch. >> >> >> >> Into which tracker should that go? >> CogVM or Pharo? >> > the build job? > > https://ci.lille.inria.fr/pharo/view/Cog/job/Cog%20Git%20Tracker/ > > > >> Best regards >> Stefan >> >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> >> > > > > -- > Best regards, > Igor Stasenko. >
