(search/replace in a working copy) OR (corruptible .svn directories)

Hi,

Very often I need to recursively search/replace several files of the
same type.
If I'm not extremely careful with the file selection pattern, the
search/replace
will corrupt the .svn directories. This scenario plays itself over and
over
again. It's daily bread for mid-to-large projects and the .svn directory
mechanism is very vulnerable to it.

Has this hit anybody else?

A significant improvement would be to at least move out-of-tree the
local copies
of the original file revision contents. This could be done by storing in
the
.svn directories only pointers to the repo/revision and caching the repo
data in
an out-of-tree "cache database" that the svn client would query before
going to
the repo. The location of the cache DB could very well be a client-side
setting.

Thanx
-alessio

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 21 11:07:31 2006