From: "akuster" <akuster808@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-security][dunfell][PATCH 2/2] README: updated branch for Dunfell
Date: Sat, 17 Oct 2020 07:18:09 -0700 [thread overview]
Message-ID: <20201017141809.20092-2-akuster808@gmail.com> (raw)
In-Reply-To: <20201017141809.20092-1-akuster808@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
README | 12 ++++++------
meta-integrity/README.md | 8 ++------
meta-security-compliance/README | 8 ++++----
meta-security-isafw/README.md | 4 ++--
meta-tpm/README | 8 ++++----
5 files changed, 18 insertions(+), 22 deletions(-)
diff --git a/README b/README
index f223fee..19b07c7 100644
--- a/README
+++ b/README
@@ -10,27 +10,27 @@ Dependencies
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
- branch: master
+ branch: dunfell
revision: HEAD
prio: default
URI: git://git.openembedded.org/meta-openembedded/meta-oe
- branch: master
+ branch: dunfell
revision: HEAD
prio: default
URI: git://git.openembedded.org/meta-openembedded/meta-perl
- branch: master
+ branch: dunfell
revision: HEAD
prio: default
URI: git://git.openembedded.org/meta-openembedded/meta-python
- branch: master
+ branch: dunfell
revision: HEAD
prio: default
URI: git://git.openembedded.org/meta-openembedded/meta-networking
- branch: master
+ branch: dunfell
revision: HEAD
prio: default
@@ -60,7 +60,7 @@ Maintenance
Send pull requests, patches, comments or questions to yocto@lists.yoctoproject.org
When sending single patches, please using something like:
-'git send-email -1 --to yocto@lists.yoctoproject.org --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to yocto@lists.yoctoproject.org --subject-prefix=meta-security][dunfell][PATCH'
These values can be set as defaults for this repository:
diff --git a/meta-integrity/README.md b/meta-integrity/README.md
index 4607948..f08a164 100644
--- a/meta-integrity/README.md
+++ b/meta-integrity/README.md
@@ -10,15 +10,11 @@ Dependencies
This layer depends on:
URI: git://git.openembedded.org/bitbake
- branch: master
+ branch: dunfell
URI: git://git.openembedded.org/openembedded-core
layers: meta
- branch: master
-
- URI: git://github.com/01org/meta-security/meta-integrate
- layers: security-framework
- branch: master
+ branch: dunfell
Patches
diff --git a/meta-security-compliance/README b/meta-security-compliance/README
index 320f856..86a95fb 100644
--- a/meta-security-compliance/README
+++ b/meta-security-compliance/README
@@ -9,16 +9,16 @@ Dependencies
This layer depends on:
URI: git://git.openembedded.org/bitbake
- branch: master
+ branch: 1.48
URI: git://git.openembedded.org/openembedded-core
layers: meta
- branch: master
+ branch: dunfell
or
URI: git://git.yoctoproject.org/poky
- branch: master
+ branch: dunfell
@@ -28,7 +28,7 @@ Maintenance
Send pull requests, patches, comments or questions to yocto@yoctoproject.org
When sending single patches, please using something like:
-'git send-email -1 --to yocto@yoctoproject.org --subject-prefix=meta-security-compliance][PATCH'
+'git send-email -1 --to yocto@yoctoproject.org --subject-prefix=meta-security-compliance][dunfell][PATCH'
Layer Maintainer: Armin Kuster <akuster808@gmail.com>
diff --git a/meta-security-isafw/README.md b/meta-security-isafw/README.md
index 16041cb..48db167 100644
--- a/meta-security-isafw/README.md
+++ b/meta-security-isafw/README.md
@@ -78,12 +78,12 @@ Patches
end pull requests, patches, comments or questions to yocto@lists.yoctoproject.org
When sending single patches, please using something like:
-'git send-email -1 --to yocto@lists.yoctoproject.org --subject-prefix=meta-security-isafw][PATCH'
+'git send-email -1 --to yocto@lists.yoctoproject.org --subject-prefix=meta-security-isafw][dunfell][PATCH'
These values can be set as defaults for this repository:
$ git config sendemail.to yocto@lists.yoctoproject.org
-$ git config format.subjectPrefix meta-security-isafw][PATCH
+$ git config format.subjectPrefix meta-security-isafw][dunfell][PATCH
Now you can just do 'git send-email origin/master' to send all local patches.
diff --git a/meta-tpm/README b/meta-tpm/README
index dd662b3..90e211c 100644
--- a/meta-tpm/README
+++ b/meta-tpm/README
@@ -9,12 +9,12 @@ Dependencies
This layer depends on:
URI: git://git.openembedded.org/openembedded-core
- branch: master
+ branch: dunfell
revision: HEAD
prio: default
URI: git://git.openembedded.org/meta-openembedded/meta-oe
- branch: master
+ branch: dunfell
revision: HEAD
prio: default
@@ -41,12 +41,12 @@ Maintenance
Send pull requests, patches, comments or questions to yocto@yoctoproject.org
When sending single patches, please using something like:
-'git send-email -1 --to yocto@yoctoproject.org --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to yocto@yoctoproject.org --subject-prefix=meta-security][dunfell][PATCH'
These values can be set as defaults for this repository:
$ git config sendemail.to yocto@yoctoproject.org
-$ git config format.subjectPrefix meta-security][PATCH
+$ git config format.subjectPrefix meta-security][dunfell][PATCH
Now you can just do 'git send-email origin/master' to send all local patches.
--
2.17.1
prev parent reply other threads:[~2020-10-17 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 14:18 [meta-security][dunfell][PATCH 1/2] ibmswtpm2: fix QA warning akuster
2020-10-17 14:18 ` akuster [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=20201017141809.20092-2-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=yocto@lists.yoctoproject.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