[website] 04/04: Add 'Commit policy' section.
Bas Couwenberg
sebastic at xs4all.nl
Sat Feb 15 01:30:16 UTC 2014
This is an automated email from the git hooks/post-receive script.
sebastic-guest pushed a commit to branch master
in repository website.
commit 63b210a175e293137cfcf1d25e83a249bcffffcc
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date: Sat Feb 15 02:25:00 2014 +0100
Add 'Commit policy' section.
---
policy.xml | 35 ++++++++++++++++++++++++++++++++---
1 file changed, 32 insertions(+), 3 deletions(-)
diff --git a/policy.xml b/policy.xml
index 6448d72..d155b67 100644
--- a/policy.xml
+++ b/policy.xml
@@ -1097,9 +1097,38 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, /usr/sbin/cowbuilder
</sect3>
<sect3 id="git-commit-policy">
<title>Commit policy</title>
- <para>
- ...
- </para>
+ <sect4>
+ <title>Single change per commit</title>
+ <para>
+ This is true for any VCS, but it won't hurt saying it again:
+ please include only one change in each commit.
+ </para>
+ <para>
+ <command>git-gui</command>'s and
+ <command>git add</command> <option>-p</option>'s
+ ability to stage single lines (or hunks) is a huge help
+ if you have done several unrelated changes in the sources.
+ </para>
+ </sect4>
+ <sect4>
+ <title>Changelog maintenance</title>
+ <para>
+ Some prefer to update <filename>debian/changelog</filename>
+ with each commit, while others prefer to do that only at release time
+ by using <command>gbp-dch</command>.
+ </para>
+ <para>
+ The current group policy states that
+ whenever you stop working on a package,
+ the changelog should be updated and pushed.
+ </para>
+ <para>
+ That is, either include the changelog entry with each commit using
+ <command>dch</command>,
+ or finish your work by updating the changelog, e.g. using
+ <command>gbp-dch</command>.
+ </para>
+ </sect4>
</sect3>
<sect3 id="git-remove-package">
<title>Removing packages</title>
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-grass/website.git
More information about the Pkg-grass-devel
mailing list