-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CMF Tests Summarizer wrote:
Summary of messages to the cmf-tests list.
Period Sun Aug 16 12:00:00 2009 UTC to Mon Aug 17 12:00:00 2009 UTC.
There were 4 messages: 4 from CMF Tests.
Test failures
-
Subject: FAILED (failures=1) :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 17, 2009, at 16:45 , Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 :
Linux
From: CMF Tests
Date: Sun Aug 16 21:17:25 EDT 2009
URL:
On Mon, Aug 17, 2009 at 7:56 AM, Jens Vagelpohlj...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 17, 2009, at 16:45 , Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.2 : Linux
On Mon, Aug 17, 2009 at 5:48 PM, Alec Mitchellap...@columbia.edu wrote:
It may make the
most sense to remove the Quoted Printable config from MailHost and
just punt this decision to some future release.
Currently your changes only apply to Zope trunk aka 2.13 which is in
early development. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Aug 17, 2009, at 17:52 , Hanno Schlichting wrote:
If you get the permission to backport these changes to 2.12 (or be
bold enough to just do it, since they seem to make sense) you could
back out this one change, so the 2.12 would keep the
On 2009-8-17 17:48, Alec Mitchell wrote:
Exactly. The failures are essentially cosmetic, I can fix them either
by removing the Quoted Printable configuration from MailHost or by
changing the CMF tests to expect Quoted Printable instead of Base64.
Quoted Printable is easily readable/debuggable
