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

Re: Why rewrite the Subversion working copy?

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Wed, 23 Apr 2008 15:10:58 -0400

Eric Gillespie <epg_at_pretzelnet.org> writes:
> Michael Sinz <Michael.Sinz_at_sinz.org> writes:
>> -- The ability to centralize control/manage client configuration and
>> behaviors such as the autoprops, security behaviors (saving passwords,
>> SSL certificate handling, commit note templates, etc)
> Absolutely. Maybe someone wants to take on repo-based
> configuration/inheritable props/whatever for 1.6?

Inheritable props are pretty hard with current libsvn_wc (maybe not
impossible, just hard). They'll be a lot easier in wc-ng. Hmmm. We
don't want wc-ng to become a "feature sink", if you know what I mean.
On the other hand, the idea is to save work...

Sigh. I should really write up the plan I had a while back for
implementing them with the current libsvn_wc; klugey, but probably
workable. Right now I'm pulling a Branko.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-23 21:11:15 CEST

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.