--- Begin Message ---
Forgot to copy the Pharo dev list.
Begin forwarded message:
> From: Reg Krock
> Subject: FileSystem and references to FIle
> Date: 8 January, 2019 at 2:05:15 PM EST
> To: Guillermo Polito , Sven Van Caekenberghe
>
> Cc: Dale Henrichs , Martin McClure
>
>
> Guille,
>
Hi,
IceCommitish>>#validateCanMerge has the warning: ''Experimental Feature:
merge when there is a dirty working copy. Could cause a loss of your local
changes. Please commit before merge.''. Are there some known situations
when code can be lost?
I'm asking because in releaser (
Le mar. 8 janv. 2019 à 17:36, Guillermo Polito
a écrit :
> Hi Eliot,
>
> Thanks for looking into this, see inline.
>
> On Tue, Jan 8, 2019 at 4:46 PM Eliot Miranda
> wrote:
>
>> Hi Guille,
>>
>> On Jan 8, 2019, at 3:19 AM, Guillermo Polito
>> wrote:
>>
>> Hi all,
>>
>> I was checking issue
Done ! Happy new year!
El mar., 8 de ene. de 2019 15:05, Jigyasa Grover
escribió:
> Voted, Good Luck !
>
> On Mon, Jan 7, 2019 at 12:01 PM ducasse wrote:
>
>> Hi
>>
>> there is a competition for the mooc loved by its users: you can vote for
>> the Pharo mooc at
>>
>>
>>
Voted, Good Luck !
On Mon, Jan 7, 2019 at 12:01 PM ducasse wrote:
> Hi
>
> there is a competition for the mooc loved by its users: you can vote for
> the Pharo mooc at
>
>
> https://docs.google.com/forms/d/e/1FAIpQLSfPtKTnyRqJDlJ53A7Ml-nVoKRrz9ijz9LnYRAVBXInzeqrjg/viewform
>
> Stef
>
>
>
>
Hi Eliot,
Thanks for looking into this, see inline.
On Tue, Jan 8, 2019 at 4:46 PM Eliot Miranda
wrote:
> Hi Guille,
>
> On Jan 8, 2019, at 3:19 AM, Guillermo Polito
> wrote:
>
> Hi all,
>
> I was checking issue https://pharo.fogbugz.com/f/cases/19852 which is
> about the problems that arise
Hi Guille,
> On Jan 8, 2019, at 3:19 AM, Guillermo Polito
> wrote:
>
> Hi all,
>
> I was checking issue https://pharo.fogbugz.com/f/cases/19852 which is about
> the problems that arise when we move an image of location, and moreover when
> we move it between different platforms (windows to
--- Begin Message ---
There is a new Pharo build available!
The status of the build #107 was: FAILURE.
The Pull Request #2179 was integrated:
"22871-MC-makes-dirty-more-packages-than-expected"
Pull request url: https://github.com/pharo-project/pharo/pull/2179
Issue Url:
--- Begin Message ---
There is a new Pharo build available!
The status of the build #4 was: FAILURE.
Could not extract further issue information from commit message: temporary
using 70 vm (since we do not have a 80 vm yet)
Build Url:
There is a new Pharo build available!
The status of the build #3 was: FAILURE.
Could not extract further issue information from commit message: ensure version
number
Build Url:
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/Pharo8.0/3/
There is a new Pharo build available!
The status of the build #106 was: SUCCESS.
The Pull Request #1985 was integrated:
"22669-UFFI-structures-are-not-recalculated-on-system-startup"
Pull request url: https://github.com/pharo-project/pharo/pull/1985
Issue Url:
There is a new Pharo build available!
The status of the build #105 was: SUCCESS.
The Pull Request #2178 was integrated:
"22870-Remove-Compiler-packages-from-Pharo"
Pull request url: https://github.com/pharo-project/pharo/pull/2178
Issue Url: https://pharo.fogbugz.com/f/cases/22870
Build Url:
Thanks Esteban
I saw your feedback and I will go over it soon. Just busy deprecating my google
accounts and other job duties.
Stef
Thanks guille for this analysis.
I would move it to Pharo 8.0
Now I think that we should revive your analysis on state because I would love
to have first class objects with a good and nice logic for such
cases and others.
The lifetime of a variable looks more complex than it looks.
> On 8
Hi all,
I was checking issue https://pharo.fogbugz.com/f/cases/19852 which is about
the problems that arise when we move an image of location, and moreover
when we move it between different platforms (windows to linux or mac for
example).
The problem are dangling file references pointing to
There is a new Pharo build available!
The status of the build #104 was: SUCCESS.
The Pull Request #2176 was integrated:
"22867-Add-a-comment-to-Metacello-cypress-recent-fix"
Pull request url: https://github.com/pharo-project/pharo/pull/2176
Issue Url: https://pharo.fogbugz.com/f/cases/22867
16 matches
Mail list logo