diff options
author | Armin Kuster <akuster808@gmail.com> | 2017-09-23 07:45:49 -0700 |
---|---|---|
committer | Martin Jansa <Martin.Jansa@gmail.com> | 2017-10-17 10:40:25 +0000 |
commit | d8f82c4373c7ee7c9d6a93dc517d8847ade2da6a (patch) | |
tree | 59e7bb33b808de510bd93086de53fe16a9a375bb /meta-networking/MAINTAINERS | |
parent | 6e3fc5b8d904d06e3aa77e9ec9968ab37a798188 (diff) | |
download | meta-openembedded-d8f82c4373c7ee7c9d6a93dc517d8847ade2da6a.tar.gz |
README: update maintainers list for rocko
v2:
bumped bitbake version in meta-filesystems
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Diffstat (limited to 'meta-networking/MAINTAINERS')
-rw-r--r-- | meta-networking/MAINTAINERS | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/meta-networking/MAINTAINERS b/meta-networking/MAINTAINERS index bbb2d1b5b..771c73cb0 100644 --- a/meta-networking/MAINTAINERS +++ b/meta-networking/MAINTAINERS | |||
@@ -2,13 +2,16 @@ This file contains a list of maintainers for the meta-networking layer. | |||
2 | 2 | ||
3 | Please submit any patches against meta-networking to the OpenEmbedded | 3 | Please submit any patches against meta-networking to the OpenEmbedded |
4 | development mailing list (openembedded-devel@lists.openembedded.org) with | 4 | development mailing list (openembedded-devel@lists.openembedded.org) with |
5 | '[meta-networking]' in the subject. | 5 | '[meta-networking][rocko]' in the subject. |
6 | 6 | ||
7 | When sending single patches, please use something like: | 7 | When sending single patches, please use something like: |
8 | 8 | ||
9 | git send-email -1 -M \ | 9 | git send-email -1 -M \ |
10 | --to openembedded-devel@lists.openembedded.org \ | 10 | --to openembedded-devel@lists.openembedded.org \ |
11 | --subject-prefix=meta-networking][PATCH | 11 | --subject-prefix=meta-networking][rocko][PATCH |
12 | |||
13 | rocko Branch Maintainer: | ||
14 | Armin Kuster <akuster808@gmail.com> | ||
12 | 15 | ||
13 | You may also contact the maintainers directly. | 16 | You may also contact the maintainers directly. |
14 | 17 | ||