Author: plessy
Date: 2011-03-20 01:05:30 +0000 (Sun, 20 Mar 2011)
New Revision: 6321
Modified:
trunk/community/website/docs/policy.xml
Log:
First tips: debcheckout sets up branches and options for you.
Modified: trunk/community/website/docs/policy.xml
===================================================================
--- trunk/community/website/docs/policy.xml 2011-03-20 00:38:58 UTC (rev
6320)
+++ trunk/community/website/docs/policy.xml 2011-03-20 01:05:30 UTC (rev
6321)
@@ -187,6 +187,17 @@
<para>The Git repository is not structured: each
package is in its own Git repository.
But all of them are under the same
<filename>debian-med</filename> directory.</para>
</sect2>
+
+ <sect2 id="git-tips">
+ <title>Git tips</title>
+ <para>
+ To clone and follow every branch of a git
repository containing a package that is already in the Debian archive, you can
use the <command>debcheckout</command> command with its
<command><option>--git-track='*'</option></command> option. To restrict the
tracked branch to the standard ones used by
<command>git-buildpackage</command>,
<literal>master,upstream,pristine-tar</literal> can be passed instead of the
wildcard.
+ </para>
+ <para>
+ If the <package>devscripts</package> variables
<varname>DEBEMAIL</varname> and <varname>DEBFULLNAME</varname> are set,
<command>debcheckout</command> will set <command>git</command>'s options
<varname>user.email</varname> and <varname>user.name</varname> accordingly.
+ </para>
+ </sect2>
+
<sect2 id="subversion-to-git">
<title>Migration of a source package from Subversion to
Git.</title>
<para>There is no easy way to prepare a Git repository from
our Subversion repository that would
_______________________________________________
debian-med-commit mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/debian-med-commit
