[Openmcl-devel] possible trunk instability

Gary Byers gb at clozure.com
Tue May 28 19:05:04 UTC 2013


I moved the GC stuff that I was working on into a separate
branch and restored the trunk to where it was before
I started that work, so the dust is back in a settled
state.

On Fri, 24 May 2013, Gary Byers wrote:

> And by "a day or two", I of course meant "a few days".
>
> Soon.  Honest.
>
> On Wed, 22 May 2013, Gary Byers wrote:
>
>> I'm doing some work on the GC in the CCL trunk; it's pretty likely that
>> any bugs that I introduce will not be subtle ones and that our automated
>> build system will tell us about any memory faults or cryptic nonsensical
>> errors soon after I check in the code that caused them.
>> 
>> So .. if you use the CCL trunk, you might want to refrain from
>> updating for the next few days.  I'll try to send a followup message
>> when the dust seems to have settled (in a day or two.)  At that point,
>> it'd be interesting and helpful to hear reports of ...  unsettled
>> dust; until then, it probably wouldn't be.
>> 
>> _______________________________________________
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
>> http://clozure.com/mailman/listinfo/openmcl-devel
>> 
>> 
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>
>



More information about the Openmcl-devel mailing list