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

RE: [PATCH] check name svn special properties

From: Dale Worley <dworley_at_pingtel.com>
Date: 2005-08-01 23:45:58 CEST

> From: John Peacock [mailto:jpeacock@rowman.com]
> Yes, but my objection to locating this code _in the client_ is still
> there. Say we add this to 1.3 and then for 1.4, a new svn: property
> gets added (say svn:log-template). Now our compatibility guidelines
> require that a 1.3 client must be able to communicate with a 1.4 server,
> but it doesn't have to get all of the new functionality. In this case,
> any 1.3 client must use --force to set the svn:log-template property.

I missed the message where you first mentioned this...

I see your point, but as long as it's possible for an old client to cope
transparently with "new" properties *already existing* in the repository,
that seems to me to be sufficient. I don't see any real objection to having
to use --force to *add* "new" properties. Of course, this will be a
nuisance for ongoing work, but the client can be upgraded when it is
convenient to do so.

So as long as it's clarified that unknown svn: properties will be screened
only when they are added (and not when they are already present in the
repository), I think the downward-compatibility to older clients is OK.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 1 23:49:14 2005

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

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