Skip to contentSkip to conversation

manual: clarify policy when updating a package patch

PATCH New Arnout Vandecappelle (Essensium/Mind) 2 participants 2 messages Dec 2, 2015 – Dec 16, 2015

lore
Share & tools
lore

Arnout Vandecappelle (Essensium/Mind)

author
#0 lore raw

PATCH v2 1/1 manual: clarify policy when updating a package patch

Signed-off-by Arnout Vandecappelle (Essensium/Mind) <[email protected]>
Cc Renaud AUBIN <[email protected]>

---
v2: talk about 'From header' rather than 'author' (Baruch)

---
 docs/manual/patch-policy.txt | 4 ++++
 1 file changed, 4 insertions(+)
docs/manual/patch-policy.txt +4 -0
index 6e27e71..0b4604e 100644
@@ -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 existing From header and Signed-off-by tags are not
+removed, but do update the rest of the patch comment when appropriate.
+
 At the end, the patch should look like:
 
 ---------------
Signature · 1 line
2.6.2
Applied
#1 lore raw

PATCH v2 1/1 manual: clarify policy when updating a package patch

Dear Arnout Vandecappelle (Essensium/Mind),

Quoted 7 lines · Arnout Vandecappelle (Essensium/Mind)
Signed-off-by Arnout Vandecappelle (Essensium/Mind) <[email protected]>
Cc Renaud AUBIN <[email protected]>

---
v2: talk about 'From header' rather than 'author' (Baruch)

---
 docs/manual/patch-policy.txt | 4 ++++
 1 file changed, 4 insertions(+)

Applied, thanks.

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com