[libconfig-model-dpkg-perl] 02/04: Dpkg::Patch: Author, From, Reviewed-by and Ack-by fields are now list

[dod at debian.org]

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 25fb1d9ed1e40b10dc63945d12d02e08c8ecede0
Author: Dominique Dumont <dod at debian.org>
Date:   Sun Jun 15 18:51:21 2014 +0200

    Dpkg::Patch: Author, From, Reviewed-by and Ack-by fields are now list
---
 lib/Config/Model/models/Dpkg/Patch.pl | 28 ++++++++++++++++++++--------
 1 file changed, 20 insertions(+), 8 deletions(-)

diff --git a/lib/Config/Model/models/Dpkg/Patch.pl b/lib/Config/Model/models/Dpkg/Patch.pl
index 689a384..f8dd119 100644
--- a/lib/Config/Model/models/Dpkg/Patch.pl
+++ b/lib/Config/Model/models/Dpkg/Patch.pl
@@ -71,9 +71,12 @@ If the field is missing, its implicit value is "yes" if the "Bug" field is prese
       },
       'Author',
       {
-        'type' => 'leaf',
-        'value_type' => 'uniline'
+        'cargo' => {
+          'type' => 'leaf',
+          'value_type' => 'uniline'
+        },
         'description' => 'This field can be used to record the name and email of the patch author (ex: "John Bear <foo at example.com>"). Its usage is recommended when the patch author did not add copyright notices for his work in the patch itself. It\'s also a good idea to add this contact information when the patch needs to be maintained over time because it has very little chance of being integrated upstream. This field can be used multiple times if several people authored the patch.',
+        'type' => 'list'
       },
       'Origin',
       {
@@ -89,25 +92,34 @@ If the Author field is present, the Origin field can be omitted and it\'s assume
       },
       'From',
       {
-        'type' => 'leaf',
-        'value_type' => 'uniline'
+        'cargo' => {
+          'type' => 'leaf',
+          'value_type' => 'uniline'
+        },
         'description' => 'Like Author field, this field can be used to record the name and email of the patch author (ex: "John Bear <foo at example.com>"). Its usage is recommended when the patch author did not add copyright notices for his work in the patch itself. It\'s also a good idea to add this contact information when the patch needs to be maintained over time because it has very little chance of being integrated upstream. This field can be used multiple times if several people auth [...]
+        'type' => 'list'
       },
       'Reviewed-by',
       {
-        'type' => 'leaf',
-        'value_type' => 'uniline'
+        'cargo' => {
+          'type' => 'leaf',
+          'value_type' => 'uniline'
+        },
         'description' => 'This field can be used to document the fact that the patch has been reviewed and approved by someone. It should list her name and email in the standard format (similar to the example given for the Author field). This field can be used multiple times if several people reviewed the patch.
 
 ',
+        'type' => 'list'
       },
       'Acked-by',
       {
-        'type' => 'leaf',
-        'value_type' => 'uniline'
+        'cargo' => {
+          'type' => 'leaf',
+          'value_type' => 'uniline'
+        },
         'description' => 'Synonym to Reviewd-by. This field can be used to document the fact that the patch has been reviewed and approved by someone. It should list her name and email in the standard format (similar to the example given for the Author field). This field can be used multiple times if several people reviewed the patch.
 
 ',
+        'type' => 'list'
       },
       'Last-Update',
       {

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