Skip to contentSkip to conversation

README.md: update to new patches mailing list

PATCH New Armin Kuster 1 participant 1 message Apr 9, 2024

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 README.md: update to new patches mailing list

---
 README.md                | 4 ++--
 meta-hardening/README.md | 6 +++---
 meta-integrity/README.md | 2 +-
 meta-parsec/README.md    | 6 +++---
 meta-tpm/README.md       | 6 +++---
 5 files changed, 12 insertions(+), 12 deletions(-)
README.md +2 -2
index 2d1996b..3e092a9 100644
@@ -69,10 +69,10 @@ This will activate the dynamic-layer mechanism.
 Maintenance
 ======================================
 
-Send pull requests, patches, comments or questions to [email protected]
+Send pull requests, patches, comments or questions to [email protected]  
 
 When sending single patches, please using something like:
-'git send-email -1 --to [email protected] --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to [email protected] --subject-prefix=meta-security][PATCH'
 
 These values can be set as defaults for this repository:
 
meta-hardening/README.md +3 -3
index 191253c..cc39ca4 100644
@@ -64,14 +64,14 @@ layers: meta-oe
 Maintenance
 -----------
 
-Send pull requests, patches, comments or questions to [email protected]
+Send pull requests, patches, comments or questions to [email protected]
 
 When sending single patches, please using something like:
-'git send-email -1 --to [email protected] --subject-prefix=meta-hardening][PATCH'
+'git send-email -1 --to [email protected] --subject-prefix=meta-hardening][PATCH'
 
 These values can be set as defaults for this repository:
 
-$ git config sendemail.to [email protected]
+$ git config sendemail.to [email protected]
 $ git config format.subjectPrefix meta-hardening][PATCH
 
 Now you can just do 'git send-email origin/master' to send all local patches.
meta-integrity/README.md +1 -1
index 2f30e78..c333a9f 100644
@@ -41,7 +41,7 @@ Patches
 =======
 
 For discussion or patch submission via email, use the
[email protected] mailing list. When submitting patches that way,
[email protected] mailing list. When submitting patches that way,
 make sure to copy the maintainer and add a "[meta-integrity]"
 prefix to the subject of the mails.
 
meta-parsec/README.md +3 -3
index 9b231f6..785c932 100644
@@ -244,14 +244,14 @@ systemctl start parsec
 Maintenance
 -----------
 
-Send pull requests, patches, comments or questions to [email protected]
+Send pull requests, patches, comments or questions to [email protected]
 
 When sending single patches, please using something like:
-'git send-email -1 --to [email protected] --subject-prefix=meta-parsec][PATCH'
+'git send-email -1 --to [email protected] --subject-prefix=meta-parsec][PATCH'
 
 These values can be set as defaults for this repository:
 
-$ git config sendemail.to [email protected]
+$ git config sendemail.to [email protected]
 $ git config format.subjectPrefix meta-parsec][PATCH
 
 Now you can just do 'git send-email origin/master' to send all local patches.
meta-tpm/README.md +3 -3
index 5722a92..983c753 100644
@@ -57,14 +57,14 @@ other layers needed. e.g.:
 Maintenance
 -----------
 
-Send pull requests, patches, comments or questions to [email protected]
+Send pull requests, patches, comments or questions to [email protected]  
 
 When sending single patches, please using something like:
-'git send-email -1 --to [email protected] --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to [email protected] --subject-prefix=meta-security][PATCH'
 
 These values can be set as defaults for this repository:
 
-$ git config sendemail.to [email protected]
+$ git config sendemail.to [email protected]
 $ git config format.subjectPrefix meta-security][PATCH
 
 Now you can just do 'git send-email origin/master' to send all local patches.
Signature · 1 line
2.34.1