[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svnsync "207 Multi-Status" failure with http access method and property "svn:"

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 5 Jan 2010 11:35:27 -0500

On Tue, Jan 5, 2010 at 11:28, Kylo Ginsberg <kylo_at_kylo.net> wrote:
> So one bug/enhancement here is to improve client reporting when it
> encounters a 207.
> But back to the root of my original problem: I can create a "svn:"
> property via the svn access method without any errors which then
> results in errors when accessed via the http access method.  That
> seems like a bug, yes?  But is the problem that the svn access method
> *allows* this bogus property, or that http chokes on it?

Flip a coin. One could make either argument about the root of the
problem. The bigger question is, if you code to prevent the bogus
property from being set, what will happen when you access a repository
via HTTP which already had those bogus properties set? You've stopped
people from setting them in the future, which is fine - but you still
have to handle the scenario where someone accesses the ones that were
previously set.
Received on 2010-01-05 17:36:02 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.