October 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 303

by Adrian Lienhard

Hi Gwenael, Thanks for your contribution! What Damien suggested, and which is the way to go, is to add your comments to the issue tracker and update the issue's status. That is, go to http://code.google.com/p/pharo/issues/detail?id=303 and sign in (you need a google account) and then click into the comment field at the bottom. There name the mcz files that fix the issue and change the status to Fixed. See also: http://code.google.com/p/pharo/wiki/HowToContribute Cheers, Adrian On Oct 31, 2008, at 13:39 , Gwenael Casaccio wrote: > Oups sorry : > > System-GwenaelCasaccio.ducasse.178.mcz issue 304 > System-GwenaelCasaccio.ducasse.176.mcz issue 303 > > On 10/31/08 11:55 AM, Damien Pollet wrote: >> it's best to say that in the ticket, and point to which mcz/slice >> contains your changes >> >> On Fri, Oct 31, 2008 at 11:44 AM, Gwenael >> Casaccio<mrgwen(a)gmail.com> wrote: >>> Hi guys, >>> >>> I've fixed the issu 303 >>> >>> Cheers, >>> Gwenael >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 31, 2008

Re: [Pharo-project] Issue 303

by Gwenael Casaccio

Oups sorry : System-GwenaelCasaccio.ducasse.178.mcz issue 304 System-GwenaelCasaccio.ducasse.176.mcz issue 303 On 10/31/08 11:55 AM, Damien Pollet wrote: > it's best to say that in the ticket, and point to which mcz/slice > contains your changes > > On Fri, Oct 31, 2008 at 11:44 AM, Gwenael Casaccio<mrgwen(a)gmail.com> wrote: >> Hi guys, >> >> I've fixed the issu 303 >> >> Cheers, >> Gwenael >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > >

Oct. 31, 2008

Re: [Pharo-project] Problem with initials

by StÃ©phane Ducasse

Yes the problem is that the fix of lukas and julian for the branching took .ducasse as a branch so now when we publish we should remove (for the old package) the branching information System-GwenaelCasaccio.ducasse.178.mcz -> System-GwenaelCasaccio.178.mcz Stef On Oct 31, 2008, at 12:50 PM, Damien Cassou wrote: > Hi, > > I've already seen a ".ducasse" in two commits by two different people: > > System-al.ducasse.174.mcz > System-GwenaelCasaccio.ducasse.178.mcz > > And also: > > CollectionsTests-stephane_ducasse.ducasse.98.mcz > > > I don't know what happens, but you should take care of this. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 31, 2008

Re: [Pharo-project] We will not accept any changes using initials anymore

by StÃ©phane Ducasse

Damien what lukas did is to make sure that MC convert any non letter into _ so that we do not have problems with file names. Now what would be good is to radically fix Author once for all: - do not use initials at all. - deprecate it - fix all the senders - offer a nice interface - requestName - getName (accessor) - name (with request if necessary) Stef On Oct 31, 2008, at 11:58 AM, Damien Pollet wrote: > I guess it's best to adopt CamelCase FirstnameLastname, because the > firstname.lastname format conflicts with the naming of MC branches. > I'll update the initials dialog and try to make a more complete fix of > this > > On Sat, Oct 25, 2008 at 7:47 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> done! >> Stef >> >> On Oct 25, 2008, at 8:16 PM, Dan Corneanu wrote: >> >>> On Sat, Oct 25, 2008 at 8:08 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> ascii only no space >>>> >>> >>> Maybe we should state that too on page >>> http://code.google.com/p/pharo/wiki/HowToContribute >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 31, 2008

[Pharo-project] Problem with initials

by Damien Cassou

Hi, I've already seen a ".ducasse" in two commits by two different people: System-al.ducasse.174.mcz System-GwenaelCasaccio.ducasse.178.mcz And also: CollectionsTests-stephane_ducasse.ducasse.98.mcz I don't know what happens, but you should take care of this. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 31, 2008

Re: [Pharo-project] We will not accept any changes using initials anymore

by Damien Pollet

I guess it's best to adopt CamelCase FirstnameLastname, because the firstname.lastname format conflicts with the naming of MC branches. I'll update the initials dialog and try to make a more complete fix of this On Sat, Oct 25, 2008 at 7:47 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > done! > Stef > > On Oct 25, 2008, at 8:16 PM, Dan Corneanu wrote: > >> On Sat, Oct 25, 2008 at 8:08 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> ascii only no space >>> >> >> Maybe we should state that too on page >> http://code.google.com/p/pharo/wiki/HowToContribute >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 31, 2008

Re: [Pharo-project] Issue 303

by Damien Pollet

it's best to say that in the ticket, and point to which mcz/slice contains your changes On Fri, Oct 31, 2008 at 11:44 AM, Gwenael Casaccio <mrgwen(a)gmail.com> wrote: > Hi guys, > > I've fixed the issu 303 > > Cheers, > Gwenael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 31, 2008

Re: [Pharo-project] Issue 303

by Gwenael Casaccio

On 10/31/08 11:44 AM, Gwenael Casaccio wrote: > Hi guys, > > I've fixed the issu 303 > > Cheers, > Gwenael Also the issue 304 :p I've kept the SmalltalkImage>>licenseString which contains all the information copyright and license.

Oct. 31, 2008

[Pharo-project] Issue 303

by Gwenael Casaccio

Hi guys, I've fixed the issu 303 Cheers, Gwenael

Oct. 31, 2008

Re: [Pharo-project] RBParser

by Gwenael Casaccio

I've commit a new version I've removed all the RB*Token On 10/29/08 6:21 PM, Lukas Renggli wrote: >> As I've said to you Marcus, I've worked on the RBParser/RBScanner. I've >> fixed these classes and now you can parse the entire image. At this moment >> the refactoring is not yet finished but I've made some good progress. > > Good news. > > I was not aware that you were working on RBParser. Stef told me that > you also improved the refactorings. I think you should commit and work > on the public repository to get more attention. I guess there were > many other changes going on in RB codebase in the meantime. > > Cheers, > Lukas >

Oct. 31, 2008