Patchwork [[meta-oe,meta-efl] 11/15] README: keep PATCH prefix in subject-prefix, some people filter their inbox based on that

login
register
mail settings
Submitter Martin Jansa
Date April 26, 2012, 12:50 p.m.
Message ID <ea1f6cf8a06930922641c1a6ff2873977637ac9e.1335444528.git.Martin.Jansa@gmail.com>
Download mbox | patch
Permalink /patch/26449/
State Accepted
Commit ea1f6cf8a06930922641c1a6ff2873977637ac9e
Headers show

Comments

Martin Jansa - April 26, 2012, 12:50 p.m.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
---
 meta-efl/README        |    2 +-
 meta-gpe/README        |    2 ++
 meta-initramfs/README  |    2 ++
 meta-multimedia/README |    2 +-
 meta-oe/README         |    2 +-
 meta-xfce/README       |    2 +-
 toolchain-layer/README |    2 +-
 7 files changed, 9 insertions(+), 5 deletions(-)

Patch

diff --git a/meta-efl/README b/meta-efl/README
index 41effe6..62daa0a 100644
--- a/meta-efl/README
+++ b/meta-efl/README
@@ -10,6 +10,6 @@  revision: HEAD
 
 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-efl]' in the subject'
 
-When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix meta-efl'
+When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-efl][PATCH'
 
 Interim layer maintainer: Koen Kooi <koen@dominion.thruhere.net>
diff --git a/meta-gpe/README b/meta-gpe/README
index d967dc1..220f031 100644
--- a/meta-gpe/README
+++ b/meta-gpe/README
@@ -10,4 +10,6 @@  revision: HEAD
 
 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-gpe]' in the subject'
 
+When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-gpe][PATCH'
+
 Interim layer maintainer: Koen Kooi <koen@dominion.thruhere.net>
diff --git a/meta-initramfs/README b/meta-initramfs/README
index 2cecff6..8430555 100644
--- a/meta-initramfs/README
+++ b/meta-initramfs/README
@@ -22,6 +22,8 @@  Maintenance
 Send patches / pull requests to openembedded-devel@lists.openembedded.org
 with '[meta-initramfs]' in the subject.
 
+When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-initramfs][PATCH'
+
 Layer maintainers: Andrea Adami <andrea.adami@gmail.com>
                    Paul Eggleton <paul.eggleton@linux.intel.com>
 
diff --git a/meta-multimedia/README b/meta-multimedia/README
index a60a7bc..8f90dbb 100644
--- a/meta-multimedia/README
+++ b/meta-multimedia/README
@@ -12,7 +12,7 @@  revision: HEAD
 
 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the subject'
 
-When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix meta-multimedia'
+When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-multimedia][PATCH
 
 You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
 
diff --git a/meta-oe/README b/meta-oe/README
index ed14866..4226c29 100644
--- a/meta-oe/README
+++ b/meta-oe/README
@@ -6,7 +6,7 @@  revision: HEAD
 
 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
 
-When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe'
+When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][PATCH'
 
 You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
 
diff --git a/meta-xfce/README b/meta-xfce/README
index 1a503c9..fa2bab0 100644
--- a/meta-xfce/README
+++ b/meta-xfce/README
@@ -10,6 +10,6 @@  revision: HEAD
 
 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-xfce]' in the subject'
 
-When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix meta-xfce'
+When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-xfce][PATCH'
 
 Interim layer maintainer: Andreas Müller <schnitzeltony@googlemail.com>
diff --git a/toolchain-layer/README b/toolchain-layer/README
index 15ac069..5996b6c 100644
--- a/toolchain-layer/README
+++ b/toolchain-layer/README
@@ -6,7 +6,7 @@  revision: HEAD
 
 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][toolchain-layer]' in the subject'
 
-When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer'
+When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer][PATCH'
 
 You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.