From 44aed17774293616e7c2bdceba468f26595e6ec8 Mon Sep 17 00:00:00 2001 From: skarg Date: Thu, 27 Sep 2012 20:20:36 +0000 Subject: [PATCH] updated documentation for subversion repository changes. --- bacnet-stack/doc/README.subversion | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/bacnet-stack/doc/README.subversion b/bacnet-stack/doc/README.subversion index 4f142fe1..5cccfa76 100644 --- a/bacnet-stack/doc/README.subversion +++ b/bacnet-stack/doc/README.subversion @@ -2,11 +2,13 @@ To check out the trunk from the subversion repository, 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: - 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 ========== 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 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, and create a "1.0.0" tag. Work on what will eventually be 1.1.0 continues in trunk. @@ -129,4 +131,4 @@ something that takes a long time (and you're afraid if it holding up a 1.2.0 release when you're ready to branch 1.2.0 from trunk), you can do it in isolation in branch. Generally you keep it up to date with trunk by merging changes into it all the time, which makes it easier to re-integrate -(merge back to trunk) when you're finished. \ No newline at end of file +(merge back to trunk) when you're finished.