-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/09/2009 07:12 PM, Benji York wrote:
> On Wed, Sep 9, 2009 at 12:40 PM, Christian Theune wrote:
>> On 09/09/2009 05:05 PM, Martijn Faassen wrote:
>>> * better merge tracking
>>
>> For some interpretation of "better".
>
> My team tried pretty hard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
robert rottermann wrote:
> Martijn Faassen schrieb:
>> Hi there,
>>
>> Christian Theune wrote:
>>> a long-standing issue with our mirror of svn.zope.org are the absolute
>>> URLs of externals: they require the repository to be available on a
>>> given
What about upgrading server to 1.6.
Subversion 1.6 has many new features.
>From http://subversion.tigris.org/svn_1.6_releasenotes.html :
* Improved handling of authentication data
* Repository root relative URLs
* Improvements to svn:externals
* Detection of tree conflicts
* Fi
On Wed, Sep 9, 2009 at 12:40 PM, Christian Theune wrote:
> On 09/09/2009 05:05 PM, Martijn Faassen wrote:
>> * better merge tracking
>
> For some interpretation of "better".
My team tried pretty hard to use 1.5's merge tracking and we could never
get it to work well for us.
The only advantage we
On Wed, Sep 9, 2009 at 6:40 PM, Christian Theune wrote:
> On 09/09/2009 05:05 PM, Martijn Faassen wrote:
>> Okay, no objection to upgrading the server to 1.5 now.
>
> That has been done a good while ago already (I was probably ambiguous in
> my mail).
Damn, Jens is just doing too much of an awesom
On 09/09/2009 05:05 PM, Martijn Faassen wrote:
> Jens Vagelpohl wrote:
>>
>> On Sep 9, 2009, at 15:30 , Martijn Faassen wrote:
>>
>>> Ah, I perhaps misunderstood. I figured the resolving of relative
>>> externals would be a problem with a Subversion 1.4.x client.
>>
>> There's two different issues
On Sep 9, 2009, at 17:05 , Martijn Faassen wrote:
> Jens Vagelpohl wrote:
>> SVN 1.4 clients will work with SVN 1.5 repositories in general.
>> However,
>> that's not the real issue here. The issue is the new-style externals
>> definitions that allow you to use "relative" paths. Those relative
On 2009-9-9 14:54, Hanno Schlichting wrote:
> On Wed, Sep 9, 2009 at 2:40 PM, Martijn Faassen
> wrote:
>> Christian Theune wrote:
>>> However, this requires Subversion 1.5 which we are using on the server
>>> already, but I don't know whether we assume clients are 1.5 or higher.
>>
>> I certainly
Jens Vagelpohl wrote:
>
> On Sep 9, 2009, at 15:30 , Martijn Faassen wrote:
>
>> Ah, I perhaps misunderstood. I figured the resolving of relative
>> externals would be a problem with a Subversion 1.4.x client.
>
> There's two different issues being confused here.
>
> SVN 1.4 clients will work w
The is used to identify
the encoding of the file providing the template.
This has nothing to do with the encoding of the output resource, which
is determined by the application. In the case of the Zope publisher,
Unicode output from the template is converted to UTF-8 by default, and
the charset
On Sep 9, 2009, at 15:59 , Sidnei da Silva wrote:
> On Wed, Sep 9, 2009 at 10:35 AM, Jens Vagelpohl
> wrote:
>> SVN 1.4 clients will work with SVN 1.5 repositories in general.
>> However,
>> that's not the real issue here. The issue is the new-style externals
>> definitions that allow you to
On Wed, Sep 9, 2009 at 9:13 AM, Malthe Borch wrote:
> Fabio Tranchitella wrote:
>> I hope this is the right mailing list for such a question. Why does
>> chameleon.core removes the meta tag http-equiv="content-type" from the
>> output?
>
> I have no idea why; I've asked Sidnei to clarify that parti
On Wed, Sep 9, 2009 at 10:35 AM, Jens Vagelpohl wrote:
> SVN 1.4 clients will work with SVN 1.5 repositories in general. However,
> that's not the real issue here. The issue is the new-style externals
> definitions that allow you to use "relative" paths. Those relative paths
> will not work for SVN
On Sep 9, 2009, at 15:30 , Martijn Faassen wrote:
Ah, I perhaps misunderstood. I figured the resolving of relative
externals would be a problem with a Subversion 1.4.x client.
There's two different issues being confused here.
SVN 1.4 clients will work with SVN 1.5 repositories in general.
Hanno Schlichting wrote:
> On Wed, Sep 9, 2009 at 2:40 PM, Martijn Faassen wrote:
>> Christian Theune wrote:
>>> However, this requires Subversion 1.5 which we are using on the server
>>> already, but I don't know whether we assume clients are 1.5 or higher.
>> I certainly still use a SVN 1.4.x cli
On Wed, Sep 9, 2009 at 8:31 AM, Christian Theune wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> a long-standing issue with our mirror of svn.zope.org are the absolute
> URLs of externals: they require the repository to be available on a
> given URL.
>
> I propose to use relati
On Wed, Sep 9, 2009 at 2:40 PM, Martijn Faassen wrote:
> Christian Theune wrote:
>> However, this requires Subversion 1.5 which we are using on the server
>> already, but I don't know whether we assume clients are 1.5 or higher.
>
> I certainly still use a SVN 1.4.x client, being on Ubuntu 8.04 LTS
Hi there,
On 08/12/2009 12:06 PM, Jim Fulton wrote:
>
> Right. I understood this in the original proposal. Given that it
> doesn't break the existing API, I have no major problem with it, which
> is why I didn't bother to respond in the first place. I have a small
> problem that it fattens an exi
Martijn Faassen schrieb:
> Hi there,
>
> Christian Theune wrote:
>> a long-standing issue with our mirror of svn.zope.org are the absolute
>> URLs of externals: they require the repository to be available on a
>> given URL.
>>
>> I propose to use relative URLs for externals. I guess a complete upd
Hi there,
Christian Theune wrote:
> a long-standing issue with our mirror of svn.zope.org are the absolute
> URLs of externals: they require the repository to be available on a
> given URL.
>
> I propose to use relative URLs for externals. I guess a complete update
> isn't necessary, but I'd like
On Wed, Sep 9, 2009 at 8:31 AM, Christian Theune wrote:
> As a side effect this will also make svn/svn+ssh work in a nicer way
> (IMHO) as the externals will follow the protocol of what you used for
> checkout.
I like that externals to svn:... are read-only, though I don't know
offhand whether we
While wondering about the ITraverser interface being defined by
zope.location, we noticed that the zope.location.pickling.PathPersistent
class (which is this package's only user of the interface) is decorated
with a recent BBB comment, and had been questioned by a XXX comment for
some time before t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
a long-standing issue with our mirror of svn.zope.org are the absolute
URLs of externals: they require the repository to be available on a
given URL.
I propose to use relative URLs for externals. I guess a complete update
isn't necessary, but I'd
Hi there,
What's the status of the ZTK KGS?
Is the stuff still on Jim's branch?
svn+ssh://svn.zope.org/repos/main/zopetoolkit/branches/jim-kgs/kgs
What's the plan for merging this branch?
Is documentation about it all being written to add to the Zope Toolkit
documentation?
http://docs.zope.o
Fabio Tranchitella wrote:
> I hope this is the right mailing list for such a question. Why does
> chameleon.core removes the meta tag http-equiv="content-type" from the
> output?
I have no idea why; I've asked Sidnei to clarify that particular
changeset in Chameleon (although I suspect it was jus
Summary of messages to the zope-tests list.
Period Tue Sep 8 12:00:00 2009 UTC to Wed Sep 9 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Tue Sep 8 20:43:55 EDT 2009
URL: http://
26 matches
Mail list logo
