Ryan Schmidt wrote:
> This isn't even a particularly Subversion-specific insight, but I would
> rather suggest that if you have just inherited a project which uses a
> tool which you've never used before, your first task should not be to
> declare it to be poorly organized and restructure the whole thing.
Although I agree that reorganizing should be done after gaining some
understanding of other configuration issues, and did in fact suggest reading the
entire SVN Book, I include this quote from Alexis' original e-mail:
> My confusion comes because the repository and working copy are mirror images
> of each other, all the way down to every branch and tag (of which there are
> a LOT). But based on the reading I did, I thought it was more standard to
> have the repository reflect all the branches, tags, snapshots, etc, and have
> the working copy only containing, say, the active branch.
I find it highly unlikely that there is any point in having a WC that is
anchored at the root of the repository, which is certainly what he is
describing. I suspect the original site admin had no more clue about best
practices than the poor sod who got this system dumped in his lap - Hi Alexis!
;-) A good re-evaluation of all assumptions is definitely in order; the nice
thing about a version control system is that it is possible to completely change
everything, keep the history of how it was, and go back to square one if need be...
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 2 02:04:45 2007