[Zope-dev] Unindex_Object, bug (Again)

2001-02-20 Thread Andy Dawkins
The bug with zope 2.3.0 that I reported with this mail: http://zope.nipltd.com/public/lists/dev-archive.nsf/ByKey/5FE0F6EF4EFF2299 Has made it in to 2.3.1b1 Can we please get rid of it this time?? Do I need to submit anything to the collector for this to happen? -Andy

Re: [Zope-dev] Unindex_Object, bug (Again)

2001-02-20 Thread Chris McDonough
Andy, Eek!! Please do submit this to the collector again. Apologies, - C - Original Message - From: "Andy Dawkins" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 20, 2001 7:18 AM Subject: [Zope-dev] Unindex_Object, bug (Again) The bug with zope 2.

Re: [Zope-dev] Unindex_Object, bug (Again)

2001-02-20 Thread Andy Dawkins
Chris McDonough wrote: Andy, Eek!! Please do submit this to the collector again. Apologies, - C I have submitted it to the collector with a patch, so there will be no excuses next time :) -Andy ___ Zope-Dev maillist - [EMAIL

Re: [Zope-dev] Unindex_Object, bug (Again)

2001-02-20 Thread Steve Alexander
Chris McDonough wrote: Andy, Eek!! Please do submit this to the collector again. Apologies, - C - Original Message - From: "Andy Dawkins" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, February 20, 2001 7:18 AM Subject: [Zope-dev] Unindex_Object,

Re: [Zope-dev] Unindex_Object, bug (Again)

2001-02-20 Thread Chris Withers
Steve Alexander wrote: Can we please get rid of it this time?? Do I need to submit anything to the collector for this to happen? It is already fixed in 2.3 from public CVS. But, ominously, not in the 2.3.1b1 release ;-) cheers, Chris ___

Re: [Zope-dev] Unindex_Object, bug (Again)

2001-02-20 Thread Martijn Pieters
On Tue, Feb 20, 2001 at 01:38:26PM +, Chris Withers wrote: Steve Alexander wrote: Can we please get rid of it this time?? Do I need to submit anything to the collector for this to happen? It is already fixed in 2.3 from public CVS. But, ominously, not in the 2.3.1b1

RE: [Zope-dev] Unindex_Object, bug (Again)

2001-02-20 Thread Brian Lloyd
It is already fixed in 2.3 from public CVS. But, ominously, not in the 2.3.1b1 release ;-) Probably because the fix was checked in *after* the 2.3.1b1 release. Steve was pointing out tthat the fix is on the 2.3 branch, which means it will be in the next 2.3 series release (likely to be