On Thu, Jun 26, 2008 at 10:21 PM, Steve Murphy <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-06-25 at 22:50 +0100, Grey Man wrote:
>> On Tue, Jun 24, 2008 at 4:28 PM, Steve Murphy <[EMAIL PROTECTED]> wrote:
>> > This is just a note that the fixes in the CDRfix4 and CDRfix6 branches
>> > are getting clo
On Thu, Jun 26, 2008 at 8:21 PM, Steve Murphy <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-06-25 at 22:50 +0100, Grey Man wrote:
Hi murf,
> CDR start answer end
> 112 4
> 245 6
>
> Well, time 3 does get lost, but I thought it might be nice to
> be abl
On Wed, 2008-06-25 at 22:50 +0100, Grey Man wrote:
> On Tue, Jun 24, 2008 at 4:28 PM, Steve Murphy <[EMAIL PROTECTED]> wrote:
> > This is just a note that the fixes in the CDRfix4 and CDRfix6 branches
> > are getting closer to being merged into 1.4, trunk, and 1.6.x.
> >
> > If CDR's are important
On 6/26/08, Grey Man <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 24, 2008 at 4:28 PM, Steve Murphy <[EMAIL PROTECTED]> wrote:
> > This is just a note that the fixes in the CDRfix4 and CDRfix6 branches
> > are getting closer to being merged into 1.4, trunk, and 1.6.x.
> >
> > If CDR's are important
On Tue, Jun 24, 2008 at 4:28 PM, Steve Murphy <[EMAIL PROTECTED]> wrote:
> This is just a note that the fixes in the CDRfix4 and CDRfix6 branches
> are getting closer to being merged into 1.4, trunk, and 1.6.x.
>
> If CDR's are important to you, and you ignore this notice, then
> you deserve what y
This is just a note that the fixes in the CDRfix4 and CDRfix6 branches
are getting closer to being merged into 1.4, trunk, and 1.6.x.
If CDR's are important to you, and you ignore this notice, then
you deserve what you get!
These branches address various long-standing bugs, most of which are
regr
