Update docs to reflect repository location change

collective · Jul 8, 2011 · 4dc34d1 · 4dc34d1
1 parent 3b92445
commit 4dc34d1
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 21 deletions.
diff --git a/source/introduction/developermanual.txt b/source/introduction/developermanual.txt
@@ -24,10 +24,10 @@ collective.developermanual
 --------------------------
 
 collective.developermanual_ is open-for-anyone-to-edit documentation for Plone developers in Sphinx format,
-living in `Plone's collective Subversion version control system`_ (anyone can get commmit access).
+living in `Plone's collective Github version control system`_ (anyone can get commit access).
 
-.. _collective.developermanual: https://svn.plone.org/svn/collective/collective.developermanual/trunk
-.. _Plone's collective Subversion version control system: https://dev.plone.org/collective
+.. _collective.developermanual: https://github.com/collective/collective.developermanual 
+.. _Plone's collective Github version control system: https://github.com/collective
 
 Sphinx_ is a tool that makes it easy to create intelligent and beautiful documentation, 
 written by Georg Brandl and licensed under the BSD license.

diff --git a/source/introduction/writing.txt b/source/introduction/writing.txt
@@ -44,7 +44,7 @@ human errors happen all the time.
 
 * Get the documentation source files::
 
-    svn co https://svn.plone.org/svn/collective/collective.developermanual/trunk collective.developermanual
+    git clone https://github.com/collective/collective.developermanual
 
 * Edit the file which you want to update.
 
@@ -56,7 +56,8 @@ human errors happen all the time.
 
 * Commit changes::
 
-    svn commit -m "My message what I changed"
+    git commit -m "My message what I changed"
+    git push
 
 
 Code documentation
@@ -94,22 +95,6 @@ Once you write code documentation:
    those editing the code can test the manual if changes are made;
 #. add the module to the autocheckout value in the manual's ``buildout.cfg``.
 
-
-Using GIT with collective SVN
------------------------------
-
-To find the initial commit, run the following::
-
-    svn log --stop-on-copy https://svn.plone.org/svn/collective/collective.developermanual/trunk | tail
-
-Then either get the full history (will take a while)::
-
-    git svn clone -r 85920:HEAD https://svn.plone.org/svn/collective/collective.developermanual/trunk collective.developermanual
-
-or just get the latest version::
-
-    git svn clone -r HEAD https://svn.plone.org/svn/collective/collective.developermanual/trunk collective.developermanual
-
 Asking someone to do changes for you
 ------------------------------------