SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 76 | Next

David J Murphy

"Managing Software Development with Trac and Subversion"

Best practices within the Subversion community prescribe
that each repository (that hosts a single project, as ours does) have three folders
at its root: trunk, tags, and branches. trunk is considered the mainline of the
development and it is this folder that our working copy will really be of; tags are
used to mark specific moments in time (e.g. milestones and releases), while branches
will be explored later in this chapter. Technically there is no difference between a tag
and branch in Subversion; it is just convention (mainly from its predecessor CVS)
that require these to be separate. Our initial working copy will come from the
trunk folder.
As we have already discussed we could check out our repositories, create the folders,
and commit the changes, and this is a perfectly valid approach. Instead we will
create them directly in the repository and then check out the trunk folder.
2. Type:
svn mkdir http://servername/svn/sandbox/trunk
http://servername/svn/sandbox/tags
http://servername/svn/sandbox/branches
-m "Initial repository structure"
and then press Enter.
The -m "Initial repository structure" specifies a log message for the action(s)
we are performing??”creating folders in this fashion is actually checking in the
changes directly on the server.


Pages:
64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88