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

dod pushed a commit to branch master
in repository libconfig-model-dpkg-perl.

commit 4597debd12b81b3d11ef6c793b94a68d7364b87e
Author: Dominique Dumont <d...@debian.org>
Date:   Sat Oct 17 18:23:17 2015 +0200

    fix typo in model doc
---
 lib/Config/Model/models/Dpkg/Patch.pl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/Config/Model/models/Dpkg/Patch.pl 
b/lib/Config/Model/models/Dpkg/Patch.pl
index a7f6208..7b02b15 100644
--- a/lib/Config/Model/models/Dpkg/Patch.pl
+++ b/lib/Config/Model/models/Dpkg/Patch.pl
@@ -95,7 +95,7 @@ If the field is missing, its implicit value is "yes" if the 
"Bug" field is prese
       {
         'description' => 'This field should document the origin of the patch. 
In most cases, it should be a simple URL. For patches backported/taken from 
upstream, it should point into the upstream VCS web interface when possible, 
otherwise it can simply list the relevant commit identifier (it should be 
prefixed with "commit:" in that case). For other cases, one should simply 
indicate the URL where the patch was taken from (mailing list archives, 
distribution bugtrackers, etc.) when possible.
 
-The field can be optionaly prefixed with a single keyword followed by a comma 
and a space to categorize the origin. The allowed keywords are "upstream" (in 
the case of a patch cherry-picked from the upstream VCS), "backport" (in the 
case of an upstream patch that had to be modified to apply on the current 
version), "vendor" for a patch created by Debian or another distribution 
vendor, or "other" for all other kind of patches.
+The field can be optionally prefixed with a single keyword followed by a comma 
and a space to categorize the origin. The allowed keywords are "upstream" (in 
the case of a patch cherry-picked from the upstream VCS), "backport" (in the 
case of an upstream patch that had to be modified to apply on the current 
version), "vendor" for a patch created by Debian or another distribution 
vendor, or "other" for all other kind of patches.
 
 In general, a user-created patch grabbed in a BTS should be categorized as 
"other". When copying a patch from another vendor, the meta-information (and 
hence this field) should be kept if present, or created if necessary with a 
"vendor" origin.
 

-- 
Alioth's /usr/local/bin/git-commit-notice on 
/srv/git.debian.org/git/pkg-perl/packages/libconfig-model-dpkg-perl.git

_______________________________________________
Pkg-perl-cvs-commits mailing list
Pkg-perl-cvs-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-cvs-commits

Reply via email to