dali/bacnet_stack
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated documentation for subversion repository changes.

Browse Source
This commit is contained in:
skarg
2012-09-27 20:20:36 +00:00
parent 31833ed6f7
commit 44aed17774
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bacnet-stack/doc/README.subversion
+5 -3
View File
@@ -2,11 +2,13 @@
To check out the trunk from the subversion repository, To check out the trunk from the subversion repository,
use "svn co", e.g. use "svn co", e.g.
svn co https://bacnet.svn.sourceforge.net/svnroot/bacnet/trunk/bacnet-stack/ svn checkout https://svn.code.sf.net/p/bacnet/code/trunk/bacnet-stack/
or for the stable releases: or for the stable releases:
svn co https://bacnet.svn.sourceforge.net/svnroot/bacnet/tags/bacnet-stack-0-4-0/ svn checkout https://svn.code.sf.net/p/bacnet/code/tags/bacnet-stack-0-7-1/
for Anonymous checkout, use http vs. https.
========== Configure your Subversion Client for EOL properties ========== ========== Configure your Subversion Client for EOL properties ==========
Committers need to properly configure their svn client so that Committers need to properly configure their svn client so that
@@ -90,7 +92,7 @@ $ svn commit -m "changed eol-style"
From http://stackoverflow.com/questions/16142/what-do-branch-tag-and-trunk-really-mean From http://stackoverflow.com/questions/16142/what-do-branch-tag-and-trunk-really-mean
Paraphrased and copied from gregmac: Paraphrased and copied from gregmac:
We working on what will be 1.0.0 in trunk. Once 1.0.0 is finished, We are working on what will be 1.0.0 in trunk. Once 1.0.0 is finished,
branch trunk into a new "bacnet-stack-1.0.0" branch, branch trunk into a new "bacnet-stack-1.0.0" branch,
and create a "1.0.0" tag. Work on what will eventually be 1.1.0 continues and create a "1.0.0" tag. Work on what will eventually be 1.1.0 continues
in trunk. in trunk.