CaROS/meta-openembedded
3
1
Fork 0
mirror of git://git.openembedded.org/meta-openembedded synced 2026-01-01 13:58:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

README: update to danny

Browse Source 
Signed-off-by: Eric Bénard <eric@eukrea.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
This commit is contained in:
Eric BENARD 2012-11-22 09:19:07 +00:00 committed by Eric Bénard
parent 2b2521e32d
commit f8ad0760ab
10 changed files with 38 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
meta-efl/README
View File

@ -1,15 +1,15 @@
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
URI: git://git.openembedded.org/meta-openembedded
branch: master
branch: danny
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-efl]' in the subject'
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-efl][danny]' 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][PATCH'
When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-efl][danny][PATCH'
Interim layer maintainer: Koen Kooi <koen@dominion.thruhere.net>

8
meta-gpe/README
View File

@ -1,15 +1,15 @@
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
URI: git://git.openembedded.org/meta-openembedded
branch: master
branch: danny
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-gpe]' in the subject'
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-gpe][danny]' 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'
When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-gpe][danny][PATCH'
Interim layer maintainer: Koen Kooi <koen@dominion.thruhere.net>

6
meta-initramfs/README
View File

@ -12,7 +12,7 @@ Dependencies
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
@ -20,9 +20,9 @@ Maintenance
-----------
Send patches / pull requests to openembedded-devel@lists.openembedded.org
with '[meta-initramfs]' in the subject.
with '[meta-initramfs][danny]' 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'
When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-initramfs][danny][PATCH'
Layer maintainers: Andrea Adami <andrea.adami@gmail.com>
Paul Eggleton <paul.eggleton@linux.intel.com>

8
meta-multimedia/README
View File

@ -1,16 +1,16 @@
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
URI: git://git.openembedded.org/meta-openembedded/meta-oe
branch: master
branch: danny
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the subject'
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia][danny]' 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][PATCH
When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-multimedia][danny][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.

5
meta-networking/README
View File

@ -18,7 +18,7 @@ Dependencies
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
Maintenance
@ -26,3 +26,6 @@ Maintenance
Please see the MAINTAINERS file for information on contacting the
maintainers of this layer, as well as instructions for submitting patches.
When sending single patches, please using something like
'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-networking][danny][PATCH'

6
meta-oe/README
View File

@ -1,12 +1,12 @@
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][danny]' 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][PATCH'
When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][danny][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.

8
meta-systemd/README
View File

@ -1,13 +1,13 @@
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
And we're working to break the dependency on this one:
URI: git://git.openembedded.org/meta-openembedded
branch: master
branch: danny
revision: HEAD
To make BBMASK'ing per layer possible the following directory structure is
@ -15,9 +15,9 @@ used:
$[LAYERDIR}/<layer name>/recipes-<group-name>/<recipe-name>/<recipe-name>.bbappend
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][meta-systemd]' in the subject'
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][meta-systemd][danny]' 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][meta-systemd][PATCH'
When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][meta-systemd][danny][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.

7
meta-webserver/README
View File

@ -12,7 +12,7 @@ Dependencies
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
@ -21,7 +21,10 @@ Maintenance
-----------
Send patches / pull requests to openembedded-devel@lists.openembedded.org
with '[meta-webserver]' in the subject.
with '[meta-webserver][danny]' in the subject.
When sending single patches, please using something like
'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-webserver][danny][PATCH'
Layer maintainer: Paul Eggleton <paul.eggleton@linux.intel.com>

8
meta-xfce/README
View File

@ -1,11 +1,11 @@
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
URI: git://git.openembedded.org/meta-openembedded
branch: master
branch: danny
revision: HEAD
meta-xfce depends on meta-oe and meta-multimedia in this repository.
@ -14,8 +14,8 @@ this to local.conf:
BBMASK = "meta-xfce/recipes-multimedia"
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-xfce]' in the subject'
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-xfce][danny]' 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][PATCH'
When sending single patches, please using something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-xfce][danny][PATCH'
Interim layer maintainer: Andreas Müller <schnitzeltony@googlemail.com>

6
toolchain-layer/README
View File

@ -1,12 +1,12 @@
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
branch: master
branch: danny
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][toolchain-layer]' in the subject'
Send pull requests to openembedded-devel@lists.openembedded.org with '[toolchain-layer][danny]' 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][PATCH'
When sending single patches, please use something like 'git send-email -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=toolchain-layer][danny][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.