[Python-modules-commits] [python-modules] 01/01: A little better phrasing, and fix a typo.
Barry Warsaw
barry at moszumanska.debian.org
Wed Oct 21 00:52:36 UTC 2015
This is an automated email from the git hooks/post-receive script.
barry pushed a commit to branch git-policy
in repository python-modules.
commit d7ddd704f11d97a6619774606e76d9acbfedcc05
Author: Barry Warsaw <barry at python.org>
Date: Tue Oct 20 20:52:22 2015 -0400
A little better phrasing, and fix a typo.
---
policy.rst | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/policy.rst b/policy.rst
index b040a74..f510beb 100644
--- a/policy.rst
+++ b/policy.rst
@@ -102,7 +102,7 @@ repo.
Tools
-----
-``gbp build-package`` is used to build the package, either as a source package
+``gbp buildpackage`` is used to build the package, either as a source package
for use with ``pbuilder``, ``sbuild``, etc. or as a binary package directory.
Do *not* create ``quilt`` patches directly. Instead, use ``git-dpm
checkout-patched`` to enter a patch branch, edit the files, commit them, and
@@ -138,16 +138,13 @@ Tag format
----------
Use the following ``git-dpm`` tag formats for the three branches named above.
-Put these lines at the *end* of your ``debian/.git-dpm`` file::
+These lines at the *end* of the ``debian/.git-dpm`` file will ensure the
+correct tag format for the repository.
debianTag="debian/%e%v"
patchedTag="patches/%e%v"
upstreamTag="upstream/%e%u"
-All packages which have been automatically converted from the old Subversion
-repository should already have these lines present, but you will need to add
-them for any new packages.
-
More information
----------------
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/python-modules/tools/python-modules.git
More information about the Python-modules-commits
mailing list