Hello,
while making projects in SVN complying to the repository policy I found files
which tell that their license is Zope Visible Source License, Version 1.0
(ZVSL).
Is this license a valid license in the zope.org repository?
If not I'd like to merge the following change in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11 08:52 , Michael Howitz wrote:
Hello,
while making projects in SVN complying to the repository policy I found files
which tell that their license is Zope Visible Source License, Version 1.0
(ZVSL).
Is this license a valid license in
On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11 08:52 , Michael Howitz wrote:
Hello,
while making projects in SVN complying to the repository policy I found
files which tell that their license is Zope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11 15:19 , Jim Fulton wrote:
On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11 08:52 , Michael Howitz wrote:
Hello,
while making projects in SVN complying
Am 19.04.2011 um 15:19 schrieb Jim Fulton:
On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11 08:52 , Michael Howitz wrote:
Hello,
while making projects in SVN complying to the repository policy I found
On Tue, Apr 19, 2011 at 9:23 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11 15:19 , Jim Fulton wrote:
On Tue, Apr 19, 2011 at 3:39 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/11
On 18 April 2011 17:01, Laurence Rowe l...@lrowe.co.uk wrote:
When using response.appendHeader, Zope appends the new value following
an ,\r\n\t which splits the header over multiple lines. While this
behaviour is standards compliant, it causes problems for both Varnish
[1] and Nginx [2] which
This is the summary for test reports received on the
zope-tests list between 2011-04-18 00:00:00 UTC and 2011-04-19 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
