On 2/26/07 11:40 AM, "Miller, Eric" <Eric.Miller@amd.com> wrote:
>> -----Original Message-----
>> From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com]
>>
>> Okay, that probably means that you have little influence on what this
>> external
>> application does.
>
> For the time being anyways, I have no control over this.
>
>>> How can I resolve this with svn commands and avoid temp files?
>>
>> First option should be to tell the external tool not to touch files
> (in
>> particular the write-protected content of .svn) it doesn't know about.
>> However, it might also be the other way 'round that Subversion should
> not
>> try
>> to version the contents of that directory. It depends. Unconditionally
>> removing write-protected content is a bug in that external application
>> though.
>
> Yeah well if wishes were fishes... My hands are more or less tied for
> the time being.
Aside from the issue of the external tool deciding to overwrite the original
data, the main problem is that Subversion stores its metadata within the
revisioned source tree. This would be a non-issue if we didn't have the
.svn directories. The big question in this situation is whether there is a
better workaround.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 26 18:14:18 2007