summaryrefslogtreecommitdiffstats
path: root/toolchain-layer
diff options
context:
space:
mode:
authorMartin Jansa <Martin.Jansa@gmail.com>2012-04-26 11:09:34 +0200
committerMartin Jansa <Martin.Jansa@gmail.com>2012-04-26 13:49:15 +0200
commitea1f6cf8a06930922641c1a6ff2873977637ac9e (patch)
treeb22efd930f8bc9158f7e032fa4617fed6195d270 /toolchain-layer
parent1e6431adca3b45ac710a0f8ed3b56604910af052 (diff)
downloadmeta-openembedded-ea1f6cf8a06930922641c1a6ff2873977637ac9e.tar.gz
README: keep PATCH prefix in subject-prefix, some people filter their inbox based on that
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Diffstat (limited to 'toolchain-layer')
-rw-r--r--toolchain-layer/README2
1 files changed, 1 insertions, 1 deletions
diff --git a/toolchain-layer/README b/toolchain-layer/README
index 15ac06961..5996b6c84 100644
--- a/toolchain-layer/README
+++ b/toolchain-layer/README
@@ -6,7 +6,7 @@ revision: HEAD
6 6
7Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][toolchain-layer]' in the subject' 7Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][toolchain-layer]' in the subject'
8 8
9When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer' 9When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer][PATCH'
10 10
11You 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. 11You 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.
12 12