manual: clarify policy when updating a package patch
PATCH 1/1 manual: clarify policy when updating a package patch
Cc Renaud AUBIN <[email protected]>
--- docs/manual/patch-policy.txt | 4 ++++ 1 file changed, 4 insertions(+)
docs/manual/patch-policy.txt +4 -0
@@ -106,6 +106,10 @@ upstream SCM software to generate the patch set. Otherwise, concatenate the header with the output of the +diff -purN package-version.orig/ package-version/+ command. +If you update an existing patch (e.g. when bumping the package version), +make sure the original author and existing Signed-off-by tags are not +removed. + At the end, the patch should look like: ---------------
Signature · 1 line
2.6.2
PATCH 1/1 manual: clarify policy when updating a package patch
Hi Arnout,
Quoted 11 lines · Arnout Vandecappelle (Essensium/Mind)
Cc Renaud AUBIN <[email protected]>--- docs/manual/patch-policy.txt | 4 ++++ 1 file changed, 4 insertions(+)docs/manual/patch-policy.txt +0
-0
docs/manual/patch-policy.txt upstream SCM software to generate the patch set. · line 111
Quoted 6 lines
docs/manual/patch-policy.txt +3
-0@@ -106,6 +106,10 @@ upstream SCM software to generate the patch set. Otherwise, concatenate the header with the output of the +diff -purN package-version.orig/ package-version/+ command. +If you update an existing patch (e.g. when bumping the package version), +make sure the original author and existing Signed-off-by tags are not +removed.
Since not all patches we carry have an author (From:) header this text might be a little confusing. Maybe:
... make sure the original author (the 'From:' header, when the patch has one) and existing Signed-off-by ...
It maybe also be worth a mention that not all existing patches have a sign-off tag.
baruch
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -