Patchwork add subject-prefix information to format-patch submission guide

login
register
mail settings
Submitter kim.hansen@prevas.dk
Date Sept. 10, 2013, 9:33 a.m.
Message ID <1378805594-15658-1-git-send-email-kim.hansen@prevas.dk>
Download mbox | patch
Permalink /patch/273792/
State Accepted
Delegated to: Esben Haabendal
Headers show

Comments

kim.hansen@prevas.dk - Sept. 10, 2013, 9:33 a.m.
From: Kim Højgaard-Hansen <kiho@prevas.dk>

---
 upstream.txt | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)
Esben Haabendal - Sept. 12, 2013, 7:53 a.m.
<kim.hansen@prevas.dk> writes:

> From: Kim Højgaard-Hansen <kiho@prevas.dk>
>
> ---
>  upstream.txt | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)

Merged to master, thanks.

/Esben

Patch

diff --git a/upstream.txt b/upstream.txt
index 5dbead3..6742353 100644
--- a/upstream.txt
+++ b/upstream.txt
@@ -242,12 +242,12 @@  submit changes to the project.
 Those special cases that applies cleanly could be, e.g. new recipes,
 small changes to split tasks, package tasks and so on.
 
-Let say you made a new recipe and tested it and just committed it
-locally, simply do:
+Let say you made a new recipe for the core repository, tested it and just
+committed it locally, simply do:
 
 [source,sh]
 ----
-git format-patch -1 
+git format-patch -1 --subject-prefix=core 
 ----
 
 "-1" may be replaced with a specific commitid or "-2" if you want that
@@ -255,9 +255,12 @@  last two commits in a patchfile.
 
 [source,sh]
 ----
-git format-patch -2 mypatches/
+git format-patch -2 mypatches/ --subject-prefix=core
 ----
 
+The subject prefix is needed for now to make it visible what repository
+the patch applies to.
+
 Before sending single patch files upstream make sure that you have git
 send-email configure as described above.