[oe-commits] Martin Jansa : toolchain-layer, meta-networking: README: add dylan to subject-prefix and update branch in depends

[git at git.openembedded.org]

Module: meta-openembedded.git
Branch: dylan
Commit: 2c6ca829dd29b11150dce6b5b92635e9dc7f8846
URL:    http://git.openembedded.org/?p=meta-openembedded.git&a=commit;h=2c6ca829dd29b11150dce6b5b92635e9dc7f8846

Author: Martin Jansa <Martin.Jansa at gmail.com>
Date:   Mon Apr 29 10:59:36 2013 +0200

toolchain-layer, meta-networking: README: add dylan to subject-prefix and update branch in depends

Signed-off-by: Martin Jansa <Martin.Jansa at gmail.com>

---

 meta-networking/MAINTAINERS |    2 +-
 toolchain-layer/README      |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-networking/MAINTAINERS b/meta-networking/MAINTAINERS
index 953e603..c076c79 100644
--- a/meta-networking/MAINTAINERS
+++ b/meta-networking/MAINTAINERS
@@ -8,7 +8,7 @@ When sending single patches, please use something like:
 
    git send-email -1 -M \
         --to openembedded-devel at lists.openembedded.org \
-        --subject-prefix=meta-networking][PATCH
+        --subject-prefix=meta-networking][dylan][PATCH
 
 You may also contact the maintainers directly.
 
diff --git a/toolchain-layer/README b/toolchain-layer/README
index 1f9be50..448693f 100644
--- a/toolchain-layer/README
+++ b/toolchain-layer/README
@@ -1,13 +1,13 @@
 This layer depends on:
 
 URI: git://git.openembedded.org/openembedded-core
-branch: master
+branch: dylan
 revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-oe][toolchain-layer]' in the subject'
 
 When sending single patches, please use something like:
-'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer][PATCH'
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer][dylan][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.