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

Re: reverting changes to svn-base files

From: Jonathan Manning <jmanning_at_alisa-jon.net>
Date: 2004-05-03 21:53:48 CEST

Ben Collins-Sussman wrote:

>On Mon, 2004-05-03 at 10:49, Jonathan Manning wrote:
>>The problem is, this also changes all the svn-base files in the working
>>repository. I've tried some other variations (-not -name \*.svn-base
>>-and -not -name \*.svn-work) (| grep -v .svn |). Hopefully we'll get
>>used to using these soon, but it's been a difficult habit to break.
>The .svn/text-base/ files are read-only files for exactly this reason.
>How is it that your command successfully edits them?
No idea.

I did confirm the files are read-only.
I'm not using sudo, or any special account.

I just triple checked - running just the perl command seems to change
the files without complaint.
cd .svn/text-base/
perl -pi -e 's/string1/string2/' *

All files changed, despite being read-only.

I thought it might be something funky with OSX, but the same thing
occurs on my Linux system as well.

It seems perl ignores read-only. Frustrating. I'll have to find a new
command for global updates.

In any case, is there any hope of getting a variation of the cleanup
command that refreshes the text-base files? It's a huge pain dealing
with these broken WC's, and the only way to fix it is to do a fresh
checkout and risk losing all the local changes.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 3 21:54:25 2004

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.