Subversion - Reference to a project without checking it out?

Yes, this is what svn:externals is for. You still need a copy of project B, but it resides in it's own, separate repository.

Thanks - that's exactly what I need. – Finglas Nov 10 '09 at 14:36 Should be noted that its still a checkout though i.e. If you so chose you could (in theory) commit changes from the external bit (to its repository).

– Murph Nov 10 '09 at 14:41 Yeah that's fine - I'm the sole author of both projects so its fine. I just didn't want to manage two separate versions. – Finglas Nov 10 '09 at 14:48 2 But be careful.

If you don't specify an explicit revision, snv externals always point to the actual head revision. That means, if you ever go back to a specific revision of project A, this will still reference the now actual head revision of project B. – tangens Nov 10 '09 at 16:44.

If both projects live in the same repository, then simply check out a directory that contains BOTH projects. For example, lets say the svn repository starts with a directory called "trunk", and this directory contains projectA and projectB directories. If you check out "trunk", then you will be able to work on A, or B and get notified of changes in both projects when you update "trunk".

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.