[website] 02/03: Document reason for --set-upstream option when pushing.

[Sebastiaan Couwenberg]

This is an automated email from the git hooks/post-receive script.

sebastic pushed a commit to branch master
in repository website.

commit 2aaa30d5f8b88dd8a519f28d592705ea33908d7c
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date:   Thu Sep 3 22:35:45 2015 +0200

    Document reason for --set-upstream option when pushing.
---
 policy.xml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/policy.xml b/policy.xml
index 64f67c3..a70a969 100644
--- a/policy.xml
+++ b/policy.xml
@@ -1452,11 +1452,14 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, /usr/sbin/cowbuilder
               <link linkend="git-alioth-remote">added the remote</link>!
             </para>
             <para>
-              Push all your local changes to Alioth:
+              Push all your locally changed branches to Alioth:
 <programlisting>
 <command>git push</command> <option>--all</option> <option>--set-upstream</option>
 <command>git push</command> <option>--tags</option>
 </programlisting>
+              The <option>--set-upstream</option> option is required to have
+              the locally created branches track the changes from the upstream
+              repository on Alioth.
             </para>
           </sect5>
         </sect4>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-grass/website.git