Around about 08/11/11 14:34, Krigsman Kristian typed ...
We used it in a way so we could have a common code base for different
platforms and then we could inject the platform dependant files
into the correct place depending on what platform the user was
currently working on.
If your externals
Krigsman Kristian writes:
> I'm sorry to hear that this wasn't intentionally supported in 1.6
> since we built a structure around this feature. I also read into your
> answer that I shouldn't expect this to be fixed in any later release.
> We used it in a way so we could have a common code base
Philip Martin writes:
> It is a regression, I suppose, but I don't think we deliberately
> supported it in 1.6.
Thanks for the response.
I'm sorry to hear that this wasn't intentionally supported in 1.6
since we built a structure around this feature. I also read into your
answer that I shouldn
Jumping in after posting about this issue on collabnet forums:
http://subversion.open.collab.net/ds/viewMessage.do?dsForumId=4&dsMessageId=433779
I totally understand that the "external into external" was an happy
incident in 1.6, yet we do rely on it a lot in our code organization and
deploym
Krigsman Kristian writes:
> svnadmin create repo
> svn co file://`pwd`/repo wc
> cd wc
> mkdir -p A/B/C D
> echo text > A/B/file
> svn add A D
> echo ^/A/B E > external.prop
> echo ^/A/B/file E/file2 >> external.prop
> svn propset svn:externals -F external.prop D
So that defines both a directory
5 matches
Mail list logo
