From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
Armin Kuster <akuster808@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [rocko][PATCH][Maintainership] README: update maintainers list for rocko
Date: Sat, 23 Sep 2017 07:40:49 -0700 [thread overview]
Message-ID: <adbd04b2-8c6e-e6ae-56da-8c02da08efac@gmail.com> (raw)
In-Reply-To: <CA+chaQecv6JVKg_+04FiOW0iEW7B0Vdffwf3iAwYxPYAZjNZ-g@mail.gmail.com>
On 09/23/2017 12:36 AM, Martin Jansa wrote:
> Thanks for quick sign-up :)
np. I could not find the auto-renew button so I did it the old fashion way.
>
> I've noticed:
>
> URI: git://git.openembedded.org/bitbake
> <http://git.openembedded.org/bitbake>
> - branch: master
> + branch: 1.28
>
> in meta-filesystems/README, it should be 1.36.
fixing is v2.
- armin
>
> I'll leave this change on patchwork, ML for a while, for now rocko and
> master are identical, until there is first 2.5 specific change I'll
> keep it that way (we'll fix all pending build failures until then
> hopefully).
>
> On Sat, Sep 23, 2017 at 5:02 AM, Armin Kuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>> wrote:
>
> Signed-off-by: Armin Kuster <akuster808@gmail.com
> <mailto:akuster808@gmail.com>>
> ---
> meta-filesystems/README | 12 +++++++-----
> meta-gnome/README | 11 ++++++-----
> meta-initramfs/README | 10 +++++-----
> meta-multimedia/README | 15 +++++++--------
> meta-networking/MAINTAINERS | 7 +++++--
> meta-oe/README | 10 +++++-----
> meta-perl/README | 9 +++++----
> meta-python/README | 4 ++--
> meta-webserver/README | 4 ++--
> meta-xfce/README | 11 ++++++-----
> 10 files changed, 50 insertions(+), 43 deletions(-)
>
> diff --git a/meta-filesystems/README b/meta-filesystems/README
> index d2716f8..9ddd09e 100644
> --- a/meta-filesystems/README
> +++ b/meta-filesystems/README
> @@ -10,22 +10,22 @@ Dependencies
> This layer depends on:
>
> URI: git://git.openembedded.org/bitbake
> <http://git.openembedded.org/bitbake>
> - branch: master
> + branch: 1.28
>
> URI: git://git.openembedded.org/openembedded-core
> <http://git.openembedded.org/openembedded-core>
> layers: meta
> - branch: master
> + branch: rocko
>
> URI: git://git.openembedded.org/meta-openembedded
> <http://git.openembedded.org/meta-openembedded>
> layers: meta-oe
> - branch: master
> + branch: rocko
>
> Patches
> =======
>
> Please submit any patches against the filesystems layer to the
> OpenEmbedded development mailing list
> (openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>)
> -with '[meta-filesystems]' in the subject.
> +with '[meta-filesystems][rocko]' in the subject.
>
> Maintainers List:
> physfs Andreas Müller <schnitzeltony@googlemail.com
> <mailto:schnitzeltony@googlemail.com>>
> @@ -66,8 +66,10 @@ When sending single patches, please use
> something like:
>
> git send-email -1 -M \
> --to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> \
> - --subject-prefix=meta-filesystems][PATCH
> + --subject-prefix=meta-filesystems][rocko][PATCH
>
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
>
> Table of Contents
> =================
> diff --git a/meta-gnome/README b/meta-gnome/README
> index 0c4fbd2..25ef85d 100644
> --- a/meta-gnome/README
> +++ b/meta-gnome/README
> @@ -1,16 +1,17 @@
> This layer depends on:
>
> URI: git://github.com/openembedded/oe-core.git
> <http://github.com/openembedded/oe-core.git>
> -branch: master
> +branch: rocko
> revision: HEAD
>
> URI: git://github.com/openembedded/meta-oe.git
> <http://github.com/openembedded/meta-oe.git>
> -branch: master
> +branch: rocko
> revision: HEAD
>
> -Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-gnome]' in the subject'
> +Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-gnome][rocko]' in the subject'
>
> When sending single patches, please using something like:
> -'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-gnome][PATCH'
> +'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-gnome][rocko][PATCH'
>
> -Interim layer maintainer: Martin Jansa <Martin.Jansa@gmail.com
> <mailto:Martin.Jansa@gmail.com>>
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
> diff --git a/meta-initramfs/README b/meta-initramfs/README
> index e24acf9..b7dbfef 100644
> --- a/meta-initramfs/README
> +++ b/meta-initramfs/README
> @@ -12,7 +12,7 @@ Dependencies
> This layer depends on:
>
> URI: git://github.com/openembedded/oe-core.git
> <http://github.com/openembedded/oe-core.git>
> -branch: master
> +branch: rocko
> revision: HEAD
>
>
> @@ -20,13 +20,13 @@ Maintenance
> -----------
>
> Send patches / pull requests to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> -with '[meta-initramfs]' in the subject.
> +with '[meta-initramfs][rocko]' in the subject.
>
> When sending single patches, please using something like:
> -'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-initramfs][PATCH'
> +'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-initramfs][rocko][PATCH'
>
> -Layer maintainers: Andrea Adami <andrea.adami@gmail.com
> <mailto:andrea.adami@gmail.com>>
> - Paul Eggleton <paul.eggleton@linux.intel.com
> <mailto:paul.eggleton@linux.intel.com>>
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
>
>
> License
> diff --git a/meta-multimedia/README b/meta-multimedia/README
> index cbdc1b5..b59dfe0 100644
> --- a/meta-multimedia/README
> +++ b/meta-multimedia/README
> @@ -1,21 +1,20 @@
> This layer depends on:
>
> URI: git://github.com/openembedded/oe-core.git
> <http://github.com/openembedded/oe-core.git>
> -branch: master
> +branch: rocko
> revision: HEAD
>
> URI: git://github.com/openembedded/meta-oe.git
> <http://github.com/openembedded/meta-oe.git>
> -layers: meta-oe, meta-ruby
> -branch: master
> +layers: meta-oe
> +branch: rocko
> revision: HEAD
>
> -Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-multimedia]' in the subject'
> +Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-multimedia][rocko]' in the subject'
>
> When sending single patches, please use something like:
> -'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-multimedia][PATCH
> +'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-multimedia][rocko][PATCH
>
> You are encouraged to fork the mirror on github
> https://github.com/openembedded/meta-oe/
> <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
> <http://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.
>
> -Main layer maintainers: Koen Kooi <koen@dominion.thruhere.net
> <mailto:koen@dominion.thruhere.net>>
> - Martin Jansa <martin.jansa@gmail.com
> <mailto:martin.jansa@gmail.com>>
> -
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
> diff --git a/meta-networking/MAINTAINERS b/meta-networking/MAINTAINERS
> index bbb2d1b..771c73c 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.
>
> Please submit any patches against meta-networking to the OpenEmbedded
> development mailing list
> (openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>) with
> -'[meta-networking]' in the subject.
> +'[meta-networking][rocko]' in the subject.
>
> When sending single patches, please use something like:
>
> git send-email -1 -M \
> --to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> \
> - --subject-prefix=meta-networking][PATCH
> + --subject-prefix=meta-networking][rocko][PATCH
> +
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
>
> You may also contact the maintainers directly.
>
> diff --git a/meta-oe/README b/meta-oe/README
> index 6ad87c5..dabed2f 100644
> --- a/meta-oe/README
> +++ b/meta-oe/README
> @@ -1,15 +1,15 @@
> This layer depends on:
>
> URI: git://github.com/openembedded/oe-core.git
> <http://github.com/openembedded/oe-core.git>
> -branch: master
> +branch: rocko
> revision: HEAD
>
> -Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-oe]' in the subject'
> +Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-oe][rocko]' in the subject'
>
> When sending single patches, please use something like:
> -'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-oe][PATCH'
> +'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-oe][rocko][PATCH'
>
> You are encouraged to fork the mirror on github
> https://github.com/openembedded/meta-oe/
> <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
> <http://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.
>
> -Main layer maintainer: Koen Kooi <koen@dominion.thruhere.net
> <mailto:koen@dominion.thruhere.net>>
> - Martin Jansa <martin.jansa@gmail.com
> <mailto:martin.jansa@gmail.com>>
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
> diff --git a/meta-perl/README b/meta-perl/README
> index 68160a6..cc965af 100644
> --- a/meta-perl/README
> +++ b/meta-perl/README
> @@ -52,7 +52,7 @@ Dependencies
> This layer depends on:
>
> URI: git://git.openembedded.org/openembedded-core
> <http://git.openembedded.org/openembedded-core>
> - branch: master
> + branch: rocko
> revision: HEAD
> prio: default
>
> @@ -75,12 +75,13 @@ Maintenance
> -----------
>
> Send patches / pull requests to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> -'[meta-perl]' in the subject.
> +'[meta-perl][rocko]' in the subject.
>
> When sending single patches, please using something like:
> -'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-perl][PATCH'
> +'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-perl][rocko][PATCH'
>
> -Layer maintainer: Hongxu Jia <hongxu.jia@windriver.com
> <mailto:hongxu.jia@windriver.com>>
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
>
> License
> -------
> diff --git a/meta-python/README b/meta-python/README
> index 905d5ee..43740f6 100644
> --- a/meta-python/README
> +++ b/meta-python/README
> @@ -17,12 +17,12 @@ The meta-python layer depends on:
>
> URI: git://git.openembedded.org/openembedded-core
> <http://git.openembedded.org/openembedded-core>
> layers: meta
> - branch: master
> + branch: rocko
> revision: HEAD
>
> URI: git://git.openembedded.org/meta-openembedded
> <http://git.openembedded.org/meta-openembedded>
> layers: meta-oe
> - branch: master
> + branch: rocko
> revision: HEAD
>
> Please follow the recommended setup procedures of your OE
> distribution.
> diff --git a/meta-webserver/README b/meta-webserver/README
> index 7b60630..f2928ab 100644
> --- a/meta-webserver/README
> +++ b/meta-webserver/README
> @@ -13,14 +13,14 @@ This layer depends on:
>
> URI: git://github.com/openembedded/oe-core.git
> <http://github.com/openembedded/oe-core.git>
> subdirectory: meta
> -branch: master
> +branch: rocko
> revision: HEAD
>
> For some recipes, the meta-oe layer is required:
>
> URI: git://github.com/openembedded/meta-oe.git
> <http://github.com/openembedded/meta-oe.git>
> subdirectory: meta-oe
> -branch: master
> +branch: rocko
> revision: HEAD
>
>
> diff --git a/meta-xfce/README b/meta-xfce/README
> index 33ef509..3367797 100644
> --- a/meta-xfce/README
> +++ b/meta-xfce/README
> @@ -1,11 +1,11 @@
> This layer depends on:
>
> URI: git://github.com/openembedded/oe-core.git
> <http://github.com/openembedded/oe-core.git>
> -branch: master
> +branch: rocko
> revision: HEAD
>
> URI: git://github.com/openembedded/meta-oe.git
> <http://github.com/openembedded/meta-oe.git>
> -branch: master
> +branch: rocko
> revision: HEAD
> meta-xfce depends on meta-oe, meta-gnome and meta-multimedia in
> this repository.
>
> @@ -14,9 +14,10 @@ this to local.conf:
>
> BBMASK = "meta-xfce/recipes-multimedia"
>
> -Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-xfce]' in the subject'
> +Send pull requests to openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org> with
> '[meta-xfce][rocko]' in the subject'
>
> When sending single patches, please using something like:
> -'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-xfce][PATCH'
> +'git send-email -M -1 --to
> openembedded-devel@lists.openembedded.org
> <mailto:openembedded-devel@lists.openembedded.org>
> --subject-prefix=meta-xfce][rocko][PATCH'
>
> -Interim layer maintainer: Andreas Müller
> <schnitzeltony@googlemail.com <mailto:schnitzeltony@googlemail.com>>
> +rocko Branch Maintainer:
> +Armin Kuster <akuster808@gmail.com <mailto:akuster808@gmail.com>>
> --
> 2.7.4
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> <mailto:Openembedded-devel@lists.openembedded.org>
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> <http://lists.openembedded.org/mailman/listinfo/openembedded-devel>
>
>
prev parent reply other threads:[~2017-09-23 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 3:02 [rocko][PATCH][Maintainership] README: update maintainers list for rocko Armin Kuster
2017-09-23 7:36 ` Martin Jansa
2017-09-23 14:40 ` akuster808 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adbd04b2-8c6e-e6ae-56da-8c02da08efac@gmail.com \
--to=akuster808@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox