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

Re: Log Message Templates vs Server->Client Configuration.

From: Greg Stein <gstein_at_lyra.org>
Date: 2005-05-17 11:03:57 CEST

On Tue, May 17, 2005 at 11:02:17AM +0200, Branko ??ibej wrote:
> kfogel@collab.net wrote:
> >For 1.3, we've been talking as though log message templates
> >unquestionably depend on coming up with some sort of generic
> >server->client configuration transmission mechanism.
> You know, I'm totally against adding a server->client transmission
> channel that's useful only for log message templates. Whatever we decide
> to do, even if it's only *used* for log templates in 1.3, must be
> designed so that the same mechanism can be extended for other uses.
> Otherwise we're headed for the proverbial maze of twisty little
> passages, all alike.


> Users also want to be able to define autoprops on the server, either
> per-repository or per-directory. The problems are much the same as with
> log message templates, except that you'd have to somehow get at
> autoprops when you "svn add", not when you "svn commit".

Attach "provisional" properties to files when they are added. Those props
can come from a dirprop, a per-repos config, or whatever. At commit time,
if those autoprops have changed on the server, then just bail out of the
commit with an "out of date" messages. The user does an "svn up" and the
provisional props get updated to a more recent copy.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 17 11:19:41 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.