[Pharo-dev] [Pharo 7.0-dev] Build #643: 21470 Fix lint issue in AnnouncementSet

There is a new Pharo build available! The status of the build #643 was: SUCCESS. The Pull Request #1005 was integrated: "21470 Fix lint issue in AnnouncementSet" Pull request url: https://github.com/pharo-project/pharo/pull/1005 Issue Url: https://pharo.fogbugz.com/f/cases/21470 Build

[Pharo-dev] [Pharo 7.0-dev] Build #642: 21463-reduce-unimplemented-messages-send-by-removing-dead-code

There is a new Pharo build available! The status of the build #642 was: SUCCESS. The Pull Request #998 was integrated: "21463-reduce-unimplemented-messages-send-by-removing-dead-code" Pull request url: https://github.com/pharo-project/pharo/pull/998 Issue Url:

Re: [Pharo-dev] How to use git with gitfiletree

On 03/02/2018 10:14 AM, Sean P. DeNigris wrote: Peter Uhnák wrote you mean that gitFILETREE:// would somehow use TONEL? No, I mean a configuration file specifying tonel, like we currently have .filetree files in every directory with filetree things in it. Embedding the serialization format

Re: [Pharo-dev] Integration deadlock?

I did a file out because the PR was totally literally broken. I change theMetaClass and theNonMetaClass to classSide instanceSide On Fri, Mar 2, 2018 at 4:52 PM, Denis Kudriashov wrote: > Did you really saw that Calypso was affected? > I do not know how to review this

Re: [Pharo-dev] How to use git with gitfiletree

Peter Uhnák wrote > you mean that gitFILETREE:// would somehow use TONEL? No, I mean a configuration file specifying tonel, like we currently have .filetree files in every directory with filetree things in it. Embedding the serialization format in a domain spec seems like a really bad idea.

[Pharo-dev] [Isssue tracker] Name change: Manuscript

Hello, Many of you are already wondering why you get spammed by “manuscript.com”. The reason is that Fog Creek Software changed the name of FogBugz to “Manuscript”. The old URLs are still valid, *but* they started to send all emails with the manuscript name instead some time ago. We have

[Pharo-dev] [Issue Tracker] lots of "auto close" happening

Hello, As you might now, we automatically close issue tracker entries after 1 year of in-activity. Due to two factors (the job doing it not working since 1 month *and* now being 1 year after we started to sort issues for “has to be fixed for pharo6 yes or no”, we enter a period where *a lot*

Re: [Pharo-dev] How to use git with gitfiletree

Esteban and I have agreed on some new url patterns (and changes to Tonel)  that should make things easier, however, neither of us has had the time to implement the features ... so I guess I can only say that you need to be patient (and use whatever workarounds that apply) until these new

[Pharo-dev] [Pharo 7.0-dev] Build #641: 21460-ShiftClassInstaller-do-not-correctly-add-class-side-variables-into-the-hierarchy

There is a new Pharo build available! The status of the build #641 was: SUCCESS. The Pull Request #999 was integrated: "21460-ShiftClassInstaller-do-not-correctly-add-class-side-variables-into-the-hierarchy" Pull request url: https://github.com/pharo-project/pharo/pull/999 Issue Url:

Re: [Pharo-dev] Integration deadlock?

Did you really saw that Calypso was affected? I do not know how to review this changes now. The pull request is closed. And I doubt that I will be able to merge changes back (I do not know how to do it). 2018-03-01 16:39 GMT+01:00 Stephane Ducasse : > I have a change

Re: [Pharo-dev] How to use git with gitfiletree

2018-03-02 11:12 GMT-03:00 Peter Uhnák : > you mean that gitFILETREE:// would somehow use TONEL? That hardly seems like > a good idea. > > However there's gitlocal:// ... (which iirc handles both) but I think that's > iceberg specific. Sometimes I feel I need something like

Re: [Pharo-dev] How to use git with gitfiletree

you mean that gitFILETREE:// would somehow use TONEL? That hardly seems like a good idea. However there's gitlocal:// ... (which iirc handles both) but I think that's iceberg specific. Peter On Fri, Mar 2, 2018 at 3:08 PM, Sean P. DeNigris wrote: > Peter Uhnák wrote >

Re: [Pharo-dev] How to use git with gitfiletree

Peter Uhnák wrote > you would need something like gittonel://, which doesn't exist Shouldn't this be done via configuration (e.g. .filetree) to cover cases like `github://` where tonel/FT cannot be embedded in the URL? - Cheers, Sean -- Sent from:

Re: [Pharo-dev] How can I introduce a new package in Pharo 70

CyrilFerlicot wrote > You need to: Cool. Is this in the contribution instructions? - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] [Request for comment] Hermes package

Thanks Pablo this is cool! On Thu, Mar 1, 2018 at 4:42 PM, teso...@gmail.com wrote: > Nice Idea, I have added comments to the packages, classes and methods. This > will be in the new version that will be integrated with the new Traits > implementation. > I am still cleaning

Re: [Pharo-dev] Is Smalltalk CI working with 6.1?

Ok thanks for the information. The error was not informative so I could not really get what to do. Stef On Thu, Mar 1, 2018 at 11:32 PM, Peter Uhnák wrote: > This is because tonel is not yet supported. > > I've worked on that a bit last year but I don't know why I stopped... I

Re: [Pharo-dev] How to use git with gitfiletree

So I found my problem - old version in my way - src missing and adding it did not change So after trying retrying and retrying and the help of esteban showing me that it works on his machine I got it debugged. Now I can work. Stef On Thu, Mar 1, 2018 at 11:34 PM, Peter Uhnák