Skip to contentSkip to conversation

README: updated Maintainers list for Warrior

PATCH Superseded Armin Kuster 2 participants 4 messages May 1, 2019

v2 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 README: updated Maintainers list for Warrior

[v2]
bump bitbake to warrior version

---
 README                      |  2 +-
 meta-filesystems/README     | 12 ++++++------
 meta-gnome/README           | 10 +++++-----
 meta-initramfs/README       |  8 ++++----
 meta-multimedia/README      | 10 +++++-----
 meta-networking/MAINTAINERS | 32 +++-----------------------------
 meta-networking/README      |  6 +++---
 meta-oe/README              |  8 ++++----
 meta-perl/README            | 10 ++++------
 meta-python/README          | 12 +++++-------
 meta-webserver/README       |  8 ++++----
 meta-xfce/README            | 10 +++++-----
 12 files changed, 49 insertions(+), 79 deletions(-)
README +1 -1
index 7318f09..881115e 100644
@@ -1,6 +1,6 @@
 Collection of layers for the OE-core universe
 
-Main layer maintainer: Khem Raj <[email protected]>
+Warrior maintainer: Armin Kuster  <[email protected]>
 
 This repository is a collection of layers to suppliment OE-Core
 with additional packages, Each layer have designated maintainer
meta-filesystems/README +6 -6
index 87cb685..842da13 100644
@@ -10,30 +10,30 @@ Dependencies
 This layer depends on:
 
   URI: git://git.openembedded.org/bitbake
-  branch: master
+  branch: 1.42
 
   URI: git://git.openembedded.org/openembedded-core
   layers: meta
-  branch: master
+  branch: warrior
 
   URI: git://git.openembedded.org/meta-openembedded
   layers: meta-oe
-  branch: master
+  branch: warrior
 
 Patches
 =======
 
 Please submit any patches against the filesystems layer to the
 OpenEmbedded development mailing list ([email protected])
-with '[meta-filesystems]' in the subject.
+with '[meta-filesystems][warrior]' in the subject.
 
-Layer maintainer: Khem Raj <[email protected]>
+Warrior maintainer: Armin Kuster <[email protected]>
 
 When sending single patches, please use something like:
 
    git send-email -1 -M \
         --to [email protected] \
-        --subject-prefix=meta-filesystems][PATCH
+        --subject-prefix=meta-filesystems][warrior][PATCH
 
 
 Table of Contents
meta-gnome/README +5 -5
index 2a682e7..2e9e6bb 100644
@@ -23,16 +23,16 @@ Dependencies
 This layer depends on:
 
 URI: git://github.com/openembedded/oe-core.git
-branch: master
+branch: warrior
 revision: HEAD
 
 URI: git://github.com/openembedded/meta-oe.git
-branch: master
+branch: warrior
 revision: HEAD
 
-Send pull requests to [email protected] with '[meta-gnome]' in the subject'
+Send pull requests to [email protected] with '[meta-gnome][warrior]' in the subject'
 
 When sending single patches, please using something like:
-'git send-email -M -1 --to [email protected] --subject-prefix=meta-gnome][PATCH'
+'git send-email -M -1 --to [email protected] --subject-prefix=meta-gnome][warrior][PATCH'
 
-Layer maintainer: Andreas Müller <[email protected]>
+Warrior maintainer: Armin Kuster <[email protected]>
meta-initramfs/README +4 -4
index 79244d4..b56224e 100644
@@ -12,7 +12,7 @@ Dependencies
 This layer depends on:
 
 URI: git://github.com/openembedded/oe-core.git
-branch: master
+branch: warrior
 revision: HEAD
 
 
@@ -20,12 +20,12 @@ Maintenance
 -----------
 
 Send patches / pull requests to [email protected]
-with '[meta-initramfs]' in the subject.
+with '[meta-initramfs][warrior]' in the subject.
 
 When sending single patches, please using something like:
-'git send-email -M -1 --to [email protected] --subject-prefix=meta-initramfs][PATCH'
+'git send-email -M -1 --to [email protected] --subject-prefix=meta-initramfs][warrior][PATCH'
 
-Interm layer maintainer: Khem Raj <[email protected]>
+Warrior maintainer: Armin Kuster <[email protected]>
 
 
 License
meta-multimedia/README +5 -5
index 20f4fb8..7229948 100644
@@ -1,19 +1,19 @@
 This layer depends on:
 
 URI: git://github.com/openembedded/oe-core.git
-branch: master
+branch: warrior
 revision: HEAD
 
 URI: git://github.com/openembedded/meta-oe.git
 layers: meta-oe
-branch: master
+branch: warrior
 revision: HEAD
 
-Send pull requests to [email protected] with '[meta-multimedia]' in the subject'
+Send pull requests to [email protected] with '[meta-multimedia][warrior]' in the subject'
 
 When sending single patches, please use something like:
-'git send-email -M -1 --to [email protected] --subject-prefix=meta-multimedia][PATCH
+'git send-email -M -1 --to [email protected] --subject-prefix=meta-multimedia][warrior][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.
 
-Layer maintainer: Andreas Müller <[email protected]>
+Warrior maintainer: Armin Kuster <[email protected]>
meta-networking/MAINTAINERS +3 -29
index 5c4c4ce..c029935 100644
@@ -2,38 +2,12 @@ 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 ([email protected]) with
-'[meta-networking]' in the subject.
+'[meta-networking][warrior]' in the subject.
 
 When sending single patches, please use something like:
 
    git send-email -1 -M \
         --to [email protected] \
-        --subject-prefix=meta-networking][PATCH
+        --subject-prefix=meta-networking][warrior][PATCH
 
-You may also contact the maintainers directly.
-
-Descriptions of section entries:
-
-        M: Mail patches to: FullName <address@domain>
-        F: Files and directories with wildcard patterns.
-           A trailing slash includes all files and subdirectory files.
-           F: recipes-devtools/    all files in and below recipes-devtools
-           F: recipes-selinux/*    all files in recipes-selinux, but not below
-           One pattern per line.  Multiple F: lines acceptable.
-
-Please keep this list in alphabetical order.
-
-Maintainers List (try to look for most precise areas first)
-
-COMMON
-M:      Khem Raj <[email protected]>
-M:      "Joe MacDonald (backup)" <[email protected]>
-L:      [email protected]
-Q:      https://patchwork.openembedded.org/project/oe/
-S:      Maintained
-F:      conf
-F:      recipes-*
-
-NETKIT
-M:      Armin Kuster <[email protected]>
-F:      recipes-netkit
+Warrior Maintainer:      Armin Kuster <[email protected]>
meta-networking/README +3 -3
index e1ba27d..71b48dd 100644
@@ -18,19 +18,19 @@ Dependencies
 This layer depends on:
 
 URI: git://github.com/openembedded/openembedded-core.git
-branch: master
+branch: warrior
 revision: HEAD
 
 For some recipes, the meta-oe layer is required:
 
 URI: git://github.com/openembedded/meta-openembedded.git
 subdirectory: meta-oe
-branch: master
+branch: warrior
 revision: HEAD
 
 URI: git://github.com/openembedded/meta-openembedded.git
 subdirectory: meta-python
-branch: master
+branch: warrior
 revision: HEAD
 
 Maintenance
meta-oe/README +4 -4
index 0e9f842..1ce0915 100644
@@ -4,13 +4,13 @@ meta-oe
 This layer depends on:
 
 URI: git://github.com/openembedded/openembedded-core.git
-branch: master
+branch: warrior 
 revision: HEAD
 
-Send pull requests to [email protected] with '[meta-oe]' in the subject'
+Send pull requests to [email protected] with '[meta-oe][warrior]' in the subject'
 
 When sending single patches, please use something like:
-'git send-email -M -1 --to [email protected] --subject-prefix=meta-oe][PATCH'
+'git send-email -M -1 --to [email protected] --subject-prefix=meta-oe[warrior][PATCH'
 
 You are encouraged to fork the mirror on GitHub https://github.com/openembedded/openembedded-core
 to share your patches, this is preferred for patch sets consisting of more than one patch.
@@ -19,4 +19,4 @@ Other services like gitorious, repo.or.cz or self-hosted setups are of course ac
 '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.
 
-layer maintainer: Khem Raj <[email protected]>
+Warrior maintainer: Armin Kuster <[email protected]>
meta-perl/README +4 -6
index 67f2910..543e889 100644
@@ -52,7 +52,7 @@ Dependencies
 This layer depends on:
 
   URI: git://git.openembedded.org/openembedded-core
-  branch: master
+  branch: warrior
   revision: HEAD
   prio: default
 
@@ -75,14 +75,12 @@ Maintenance
 -----------
 
 Send patches / pull requests to [email protected] with
-'[meta-perl]' in the subject.
+'[meta-perl][warrior]' in the subject.
 
 When sending single patches, please using something like:
-'git send-email -M -1 --to [email protected] --subject-prefix=meta-perl][PATCH'
+'git send-email -M -1 --to [email protected] --subject-prefix=meta-perl][warrior][PATCH'
 
-Layer maintainers:
-    Hongxu Jia <[email protected]>
-    Tim "moto-timo" Orling <[email protected]>
+Warrior maintainers: Armin kuster <[email protected]>
 
 License
 -------
meta-python/README +5 -7
index 705b035..961efc2 100644
@@ -13,12 +13,12 @@ The meta-python layer depends on:
 
 	URI: git://git.openembedded.org/openembedded-core
 	layers: meta
-	branch: master
+	branch: warrior
 	revision: HEAD
 
 	URI: git://git.openembedded.org/meta-openembedded
 	layers: meta-oe
-	branch: master
+	branch: warrior
 	revision: HEAD
 
 Please follow the recommended setup procedures of your OE distribution.
@@ -35,15 +35,13 @@ comments and patch review. It is subscriber only, so please register
 before posting.
 
 Send pull requests to [email protected] with
-'[meta-python]' in the subject.
+'[meta-python][warrior]' in the subject.
 
 When sending single patches, please use something like: 
-'git send-email -M -1 [email protected] --subject-prefix=meta-python][PATCH'
+'git send-email -M -1 [email protected] --subject-prefix=meta-python][warrior][PATCH'
 
 Maintenance
 -------------------------
 
-Layer Maintainers:
-        Tim "moto-timo" Orling <[email protected]>
-        Derek Straka <[email protected]>
+Warrior Maintainers: Armin Kuster <[email protected]>
 
meta-webserver/README +4 -4
index 7b60630..58b6310 100644
@@ -13,14 +13,14 @@ This layer depends on:
 
 URI: git://github.com/openembedded/oe-core.git
 subdirectory: meta
-branch: master
+branch: warrior
 revision: HEAD
 
 For some recipes, the meta-oe layer is required:
 
 URI: git://github.com/openembedded/meta-oe.git
 subdirectory: meta-oe
-branch: master
+branch: warrior
 revision: HEAD
 
 
@@ -52,9 +52,9 @@ Maintenance
 -----------
 
 Send patches / pull requests to [email protected]
-with '[meta-webserver]' in the subject.
+with '[meta-webserver][warrior]' in the subject.
 
-Layer maintainer: Derek Straka <[email protected]>
+Warrior Maintainer: Armin Kuster <[email protected]>
 
 
 License
meta-xfce/README +5 -5
index 7431e8b..2362ecb 100644
@@ -1,11 +1,11 @@
 This layer depends on:
 
 URI: git://github.com/openembedded/oe-core.git
-branch: master
+branch: warrior
 revision: HEAD
 
 URI: git://github.com/openembedded/meta-oe.git
-branch: master
+branch: warrior
 revision: HEAD
 meta-xfce depends on meta-oe, meta-gnome and meta-multimedia in this repository.
 
@@ -14,9 +14,9 @@ this to local.conf:
 
 BBMASK = "meta-xfce/recipes-multimedia"
 
-Send pull requests to [email protected] with '[meta-xfce]' in the subject'
+Send pull requests to [email protected] with '[meta-xfce][warrior]' in the subject'
 
 When sending single patches, please using something like:
-'git send-email -M -1 --to [email protected] --subject-prefix=meta-xfce][PATCH'
+'git send-email -M -1 --to [email protected] --subject-prefix=meta-xfce][warrior][PATCH'
 
-Layer maintainer: Andreas Müller <[email protected]>
+Warrior Maintainer: Armin Kuster <[email protected]>
Signature · 1 line
2.7.4
#1 lore raw
Quoted 36 lines · Armin Kuster

[v2]
bump bitbake to warrior version

---
 README                      |  2 +-
 meta-filesystems/README     | 12 ++++++------
 meta-gnome/README           | 10 +++++-----
 meta-initramfs/README       |  8 ++++----
 meta-multimedia/README      | 10 +++++-----
 meta-networking/MAINTAINERS | 32 +++-----------------------------
 meta-networking/README      |  6 +++---
 meta-oe/README              |  8 ++++----
 meta-perl/README            | 10 ++++------
 meta-python/README          | 12 +++++-------
 meta-webserver/README       |  8 ++++----
 meta-xfce/README            | 10 +++++-----
 12 files changed, 49 insertions(+), 79 deletions(-)
README +1 -1
index 7318f09..881115e 100644
@@ -1,6 +1,6 @@
 Collection of layers for the OE-core universe
 
-Main layer maintainer: Khem Raj <[email protected]>
+Warrior maintainer: Armin Kuster  <[email protected]>
 
 This repository is a collection of layers to suppliment OE-Core
 with additional packages, Each layer have designated maintainer
meta-filesystems/README +0 -0
index 87cb685..842da13 100644

meta-filesystems/README Dependencies · line 13

Quoted 5 lines
meta-filesystems/README +1 -1
@@ -10,30 +10,30 @@ Dependencies
 This layer depends on:
 
   URI: git://git.openembedded.org/bitbake
-  branch: master
+  branch: 1.42

To be clear, where is 1.42 coming from?

$ git checkout warrior
Switched to branch 'warrior'
Your branch is up-to-date with 'origin/warrior'.
$ git grep BB_MIN_VER
meta/classes/sanity.bbclass:    minversion = d.getVar('BB_MIN_VERSION')
meta/conf/sanity.conf:BB_MIN_VERSION = "1.39.1"

To be clear, I'm _not_ a fan of saying we need to go that old (especially since there's no CI done with that version) but I am saying we should be consistent with the code.

Signature · 1 line
Tom
author
#2 lore raw
Quoted 43 lines · Tom Rini
Quoted 36 lines · Armin Kuster

[v2]
bump bitbake to warrior version

---
 README                      |  2 +-
 meta-filesystems/README     | 12 ++++++------
 meta-gnome/README           | 10 +++++-----
 meta-initramfs/README       |  8 ++++----
 meta-multimedia/README      | 10 +++++-----
 meta-networking/MAINTAINERS | 32 +++-----------------------------
 meta-networking/README      |  6 +++---
 meta-oe/README              |  8 ++++----
 meta-perl/README            | 10 ++++------
 meta-python/README          | 12 +++++-------
 meta-webserver/README       |  8 ++++----
 meta-xfce/README            | 10 +++++-----
 12 files changed, 49 insertions(+), 79 deletions(-)
README +1 -1
index 7318f09..881115e 100644
@@ -1,6 +1,6 @@
 Collection of layers for the OE-core universe
 
-Main layer maintainer: Khem Raj <[email protected]>
+Warrior maintainer: Armin Kuster  <[email protected]>
 
 This repository is a collection of layers to suppliment OE-Core
 with additional packages, Each layer have designated maintainer
meta-filesystems/README +0 -0
index 87cb685..842da13 100644

meta-filesystems/README Dependencies · line 13

Quoted 5 lines
meta-filesystems/README +1 -1
@@ -10,30 +10,30 @@ Dependencies
 This layer depends on:
 
   URI: git://git.openembedded.org/bitbake
-  branch: master
+  branch: 1.42

To be clear, where is 1.42 coming from?

Quoted 6 lines
$ git checkout warrior
Switched to branch 'warrior'
Your branch is up-to-date with 'origin/warrior'.
$ git grep BB_MIN_VER
meta/classes/sanity.bbclass:    minversion = d.getVar('BB_MIN_VERSION')
meta/conf/sanity.conf:BB_MIN_VERSION = "1.39.1"

How is this a problem of meta-openembedded?
its a core  and bitbake issue.

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=warrior&id=0c3423aae935c36e59d15d8bb60d7826cebc4e03
https://git.openembedded.org/bitbake/log/?h=1.42

Quoted 4 lines

To be clear, I'm _not_ a fan of saying we need to go that old (especially since there's no CI done with that version) but I am saying we should be consistent with the code.

You are helping make a case for removing the reference to what bitbake version meta-filesystems want as its the only layer that identified it needed bitbake.

The other layers in meta-openembedded don't list it.

I will send v3 to remove any reference to bitbake.

- armin

Quoted 1 line
#3 lore raw
Quoted 52 lines · On Wed, May 01, 2019 at 09:24:31AM -0700, akuster808 wrote:
Quoted 43 lines · Tom Rini
Quoted 36 lines · Armin Kuster

[v2]
bump bitbake to warrior version

---
 README                      |  2 +-
 meta-filesystems/README     | 12 ++++++------
 meta-gnome/README           | 10 +++++-----
 meta-initramfs/README       |  8 ++++----
 meta-multimedia/README      | 10 +++++-----
 meta-networking/MAINTAINERS | 32 +++-----------------------------
 meta-networking/README      |  6 +++---
 meta-oe/README              |  8 ++++----
 meta-perl/README            | 10 ++++------
 meta-python/README          | 12 +++++-------
 meta-webserver/README       |  8 ++++----
 meta-xfce/README            | 10 +++++-----
 12 files changed, 49 insertions(+), 79 deletions(-)
README +1 -1
index 7318f09..881115e 100644
@@ -1,6 +1,6 @@
 Collection of layers for the OE-core universe
 
-Main layer maintainer: Khem Raj <[email protected]>
+Warrior maintainer: Armin Kuster  <[email protected]>
 
 This repository is a collection of layers to suppliment OE-Core
 with additional packages, Each layer have designated maintainer
meta-filesystems/README +0 -0
index 87cb685..842da13 100644

meta-filesystems/README Dependencies · line 13

Quoted 5 lines
meta-filesystems/README +1 -1
@@ -10,30 +10,30 @@ Dependencies
 This layer depends on:
 
   URI: git://git.openembedded.org/bitbake
-  branch: master
+  branch: 1.42

To be clear, where is 1.42 coming from?

Quoted 6 lines
$ git checkout warrior
Switched to branch 'warrior'
Your branch is up-to-date with 'origin/warrior'.
$ git grep BB_MIN_VER
meta/classes/sanity.bbclass:    minversion = d.getVar('BB_MIN_VERSION')
meta/conf/sanity.conf:BB_MIN_VERSION = "1.39.1"
Quoted 5 lines

How is this a problem of meta-openembedded?
its a core  and bitbake issue.

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=warrior&id=0c3423aae935c36e59d15d8bb60d7826cebc4e03
https://git.openembedded.org/bitbake/log/?h=1.42

Yes, correct. Sorry for hijacking the thread, I just saw this patch which reminded me to follow up about that core issue.

Quoted 11 lines
Quoted 3 lines

To be clear, I'm _not_ a fan of saying we need to go that old (especially since there's no CI done with that version) but I am saying we should be consistent with the code.

You are helping make a case for removing the reference to what bitbake version meta-filesystems want as its the only layer that identified it needed bitbake.

The other layers in meta-openembedded don't list it.

I will send v3 to remove any reference to bitbake.

That makes the most sense, agreed. No layer should be saying what bitbake version is requires, that should be handled by the core layer.

Signature · 1 line
Tom