[med-svn] r6310 - trunk/community/website/docs

[Charles Plessy]

Author: plessy
Date: 2011-03-19 09:24:27 +0000 (Sat, 19 Mar 2011)
New Revision: 6310

Modified:
   trunk/community/website/docs/policy.xml
Log:
To show that git-buildpackage is used, add debian/gbp.conf.

I will move genereal SVN and Git help to the beginning of the
document, so I created a new section, but will eventually transfer/delete
the one below.


Modified: trunk/community/website/docs/policy.xml
===================================================================
--- trunk/community/website/docs/policy.xml	2011-03-19 09:10:36 UTC (rev 6309)
+++ trunk/community/website/docs/policy.xml	2011-03-19 09:24:27 UTC (rev 6310)
@@ -334,6 +334,25 @@
 			<para>The use of CDBS is welcome as it helps us to factorise our code. Nevertheless, please do not use complex CDBS for non-trivial packages, so that other developers can quickly understand the package when doing QA work.</para>
 			<para>It is technically possible to build CDBS packages using Debhelper without the <filename>debian/compat</filename> file. Please do not, and always include such a file according to the above guidelines.</para>
 		</sect2>
+		
+		<sect2 id="vcs">
+			<title>Version control systems</title>
+			<para>
+				We are currently using two different version control systems, Subversion and Git.
+			</para>
+			<sect3 id="vcs-svn">
+				<title>Source package stored in a Subversion repository</title>
+				<para>
+					<emphasis>This section is in construction, see <link linkend="svn-inject">below</link> for te moment.</emphasis>
+				</para>
+			</sect3>
+			<sect3 id="vcs-git">
+				<title>Source package stored in a Git repository</title>
+				<para>
+					Git repositories managed with a helper tool should announce it. For instance, to show that <command>git-buildpackage</command> is used, the package can contain a configuration file in <filename>debian/gbp.conf</filename>.
+				</para>
+			</sect3>
+		</sect2>
 
 		<sect2 id="new-package">
 			<title>Injecting a new package</title>