This is an automated email from the git hooks/post-receive script. guillem pushed a commit to branch main in repository dpkg.
View the commit online: https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=97bdc84c56ab2dbc6f5d18aca04ec387ff07d09e commit 97bdc84c56ab2dbc6f5d18aca04ec387ff07d09e Author: Guillem Jover <[email protected]> AuthorDate: Wed Aug 31 23:29:21 2022 +0200 Dpkg::Source::Package::V2: Update and clarify patch header metadata template Add missing fields, update accepted field values and syntax, and make the format clearer by distinguishing text that needs to be replaced (within «<>»), and between alternatives within «(|)» be these literal or replaceable text. --- scripts/Dpkg/Source/Package/V2.pm | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/scripts/Dpkg/Source/Package/V2.pm b/scripts/Dpkg/Source/Package/V2.pm index 68a967168..7dc558f96 100644 --- a/scripts/Dpkg/Source/Package/V2.pm +++ b/scripts/Dpkg/Source/Package/V2.pm @@ -640,12 +640,13 @@ The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: -Origin: <vendor|upstream|other>, <url of original patch> -Bug: <url in upstream bugtracker> +Origin: (upstream|backport|vendor|other), (<patch-url>|commit:<commit-id>) +Bug: <upstream-bugtracker-url> Bug-Debian: https://bugs.debian.org/<bugnumber> Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber> -Forwarded: <no|not-needed|url proving that it has been forwarded> -Reviewed-By: <name and email of someone who approved the patch> +Forwarded: (no|not-needed|<patch-forwarded-url>) +Applied-Upstream: <version>, (<commit-url>|commit:<commid-id>) +Reviewed-By: <name and email of someone who approved/reviewed the patch> Last-Update: $yyyy_mm_dd\n\n"; return $text; } -- Dpkg.Org's dpkg
