Re: svn:externals no longer "read only"?
From: David Weintraub <qazwart_at_gmail.com>
Date: Mon, 28 Jul 2008 21:21:25 -0400
I guess I am mistaken. I could have sworn that svn:externals were
How does Subversion treat externals for hooks, then?
For example I have:
svn://projects/foo/trunk and I put on this directory an svn:externals
common svn://common-projs/common
If I changed the file svn://project/foo/trunk/common/bar.java, would
svn://common-projs/common/bar.java
Or
svn://projects/foo/trunk/common/bar.java?
If it was the latter, it would make permission pre-commit hooks almost
-- David Weintraub qazwart_at_gmail.com On Mon, Jul 28, 2008 at 7:19 PM, Ryan Schmidt <subversion-2008c_at_ryandesign.com> wrote: > > On Jul 28, 2008, at 10:18, 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 don't remember that behavior, but it's been awhile since I used Subversion > 1.3. > >> I am using Subversion 1.5, on both the repository and the client. I >> notice that checking out an svn:externals sub-directory is no longer >> checked out "read-only". I also noticed that if I submit a change on >> the external directory, the changes get reflected back into the main >> directory. >> >> Was this change done on purpose? Is there a way I can emulate the >> older behavior? In certain circumstances, I don't want developers >> modifying the files for external directories. > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org For additional commands, e-mail: users-help_at_subversion.tigris.orgReceived on 2008-07-29 03:22:27 CEST |
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.