On Jul 28, 2008, at 15:40, Erik Hemdal wrote:
> David Weintraub wrote:
>
>> The last time I used Subversion (version 1.3), any directory
>> marked with svn:externals was checked out, but kept "read
>> only". That is, you could see the code, but not submit the
>> changes. I recently noticed that this no longer seems true.
>>
>> I am using Subversion 1.5,
>
> I see the same behavior using v1.4.3. If I define an external from
> a tag,
> the externals reference bypasses the pre-commit hook script on the
> external
> repository. If I try to update the tag itself, the pre-commit hook
> steps in
> and prevents it.
>
> I thought that this was due to some stupid mistake on my part or
> inexperience with svn:externals. The references I read (I checked
> the SVN
> Book as well as Willam Nagel's and Mike Mason's books) didn't give
> a clear
> picture of what is supposed to happen.
>
> Are svn:externals supposed to be read-only, or do I have to set a
> specific
> property to make it so?
I'm not aware of a way to have Subversion make the contents of
external directories read-only.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-29 01:23:14 CEST