Relative file referencing with SVN on Windows?

After some research I think I have a solution using the externals property.

After some research I think I have a solution using the externals property. Firstly using the svn:external property to reference a directory in the same repository. Set this on trunk/Proj1 to create Proj1/Docs referencing the contents of DocsDir/Proj1Docs ../DocsDir/Proj1Docs Docs This creates a disconnected child working copy inside Proj1/Docs which references /DocsDir/Proj1Docs.

Proj1/docs must not previously exist as part of the outer working copy (which makes sense since that would make it part of two working copies at once). If you edit the contents of Proj1/Docs then executing svn status inside the 'parent' working copy will list the changes to the child working copy, but you have to commit the changes to the child copy separately. Which is not a big deal.

Secondly using the svn:external property to reference to a file in the same repository. Set this on trunk/Proj1 to create Proj1/Readme. Txt which references DocsDir/Readme.txt.../DocsDir/Readme.

Txt Readme. Txt In the case of a file reference the directory in which the referenced file is imported must already be part of the owning working copy. In this case no child working copy is created and if you edit the file it is commited seamlessly as part of the owning working copy.In both cases the build machine can execute svn checkout --ignore-externals to checkout our codebase without all the bulky documentation.

Can anyone see a problem with this strategy?

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.