I would like to setup a directory structure for multiple, unrelated
projects. Each project has unrelated components (i.e. they do not need
relationships versioned). This results in a directory structure where
the versioned files/folders will be the leaves of a tree. I am unsure
of the difference between "svn mkdir" and "svnadmin create".
It seems that the 'root' of each leaf needs to be a repo created with
svnadmin and any underlying directories could be built with "svn mkdir".
Is this a reasonable method to achieve the desired structure? Are there
some ramifications I should consider?
[This is SVN 1.5.4 on an XP Prof box running Apache 2.2, running on
corporate network and using the standard network access definitions. We
already use a directory structure like this but there is no version
control. The host machine will probably change to a server OS and
hardware when the corp feels the advantage.]
Ray
______________________________________________________________________
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information which is confidential to, and/or privileged in favor of, CDI Corporation or its affiliated companies (CDI) or CDI's customers. Any review, use, reproduction, disclosure or distribution by the recipient is prohibited without prior written approval from an authorized CDI representative. This notice must appear in any such authorized reproduction, disclosure or distribution. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments. Thank you.
Received on 2008-12-01 15:57:02 CET