[Blends-commit] [SCM] blends-gsoc branch, master, updated. ad572e3a301e6b783eb5169a7fad78e9a9ffea47

[Andreas Tille]

The following commit has been merged in the master branch:
commit 1f37b694deaa730cbc05371892f0ea5f1cdb5b8c
Author: Andreas Tille <tille at debian.org>
Date:   Sun Nov 24 08:56:48 2013 +0100

    Also mention Git as alternative

diff --git a/doc/en/08_websentinel.xml b/doc/en/08_websentinel.xml
index dde32db..0648a3a 100644
--- a/doc/en/08_websentinel.xml
+++ b/doc/en/08_websentinel.xml
@@ -49,15 +49,21 @@ not yet included in Debian.
 The content of the tasks files that are used to build the metapackage
 content of a Blend is also used to determine the content of the web
 sentinel pages.  Thus you can influence the tasks pages by simply
-editing the tasks files inside the SVN of the sources of the Blends
+editing the tasks files inside the VCS of the sources of the Blends
 metapackages.  The canonical location of these tasks files inside the
 sources is (with the exception of Debian Edu that is locatet in Debian
-Edu SVN repositories) the Blends SVN at
+Edu SVN repositories) the Blends VCS at
 <informalexample>
     <programlisting>
       svn://svn.debian.org/svn/blends/projects/BLEND/trunk/SRCPKG/tasks
     </programlisting>
 </informalexample>
+or when using Git which is possible as well
+<informalexample>
+    <programlisting>
+      git://git.debian.org/git/blends/projects/BLEND.git
+    </programlisting>
+</informalexample>
 Here you can add or remove additional Dependencies to existing packages
 or you can add additional information about so called prospective
 packages.  The syntax how to do this is explained below.

-- 
Git repository for blends-gsoc code