[oe-commits] Martin Jansa : README: add -M to git send-email example

git at git.openembedded.org git at git.openembedded.org
Thu May 2 13:01:00 UTC 2013 

Module: meta-openembedded.git
Branch: dylan-next
Commit: 20a10ba02ff4c8b7afb8dc8b0edb84b7246a0c76
URL:    http://git.openembedded.org/?p=meta-openembedded.git&a=commit;h=20a10ba02ff4c8b7afb8dc8b0edb84b7246a0c76

Author: Martin Jansa <Martin.Jansa at gmail.com>
Date:   Fri Apr 26 15:33:46 2013 +0200

README: add -M to git send-email example

Signed-off-by: Martin Jansa <Martin.Jansa at gmail.com>

---

 meta-efl/README             |    3 ++-
 meta-gnome/README           |    3 ++-
 meta-gpe/README             |    3 ++-
 meta-initramfs/README       |    3 ++-
 meta-multimedia/README      |    3 ++-
 meta-networking/MAINTAINERS |    2 +-
 meta-oe/README              |    3 ++-
 meta-ruby/README            |    3 ++-
 meta-systemd/README         |    3 ++-
 meta-xfce/README            |    3 ++-
 toolchain-layer/README      |    3 ++-
 11 files changed, 21 insertions(+), 11 deletions(-)

diff --git a/meta-efl/README b/meta-efl/README
index 01f192c..7a34ad6 100644
--- a/meta-efl/README
+++ b/meta-efl/README
@@ -10,6 +10,7 @@ revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-efl][dylan]' in the subject'
 
-When sending single patches, please using something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-efl][dylan][PATCH'
+When sending single patches, please using something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-efl][dylan][PATCH'
 
 Interim layer maintainer: Koen Kooi <koen at dominion.thruhere.net>
diff --git a/meta-gnome/README b/meta-gnome/README
index d7b9e7f..9204cdf 100644
--- a/meta-gnome/README
+++ b/meta-gnome/README
@@ -10,6 +10,7 @@ revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-gnome][dylan]' in the subject'
 
-When sending single patches, please using something like 'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-gnome][dylan][PATCH'
+When sending single patches, please using something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-gnome][dylan][PATCH'
 
 Interim layer maintainer: Martin Jansa <Martin.Jansa at gmail.com>
diff --git a/meta-gpe/README b/meta-gpe/README
index 4058e72..1b59c40 100644
--- a/meta-gpe/README
+++ b/meta-gpe/README
@@ -10,6 +10,7 @@ revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-gpe][dylan]' in the subject'
 
-When sending single patches, please using something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-gpe][dylan][PATCH'
+When sending single patches, please using something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-gpe][dylan][PATCH'
 
 Interim layer maintainer: Koen Kooi <koen at dominion.thruhere.net>
diff --git a/meta-initramfs/README b/meta-initramfs/README
index 01f4f53..0d26f28 100644
--- a/meta-initramfs/README
+++ b/meta-initramfs/README
@@ -22,7 +22,8 @@ Maintenance
 Send patches / pull requests to openembedded-devel at lists.openembedded.org
 with '[meta-initramfs][dylan]' in the subject.
 
-When sending single patches, please using something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-initramfs][dylan][PATCH'
+When sending single patches, please using something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-initramfs][dylan][PATCH'
 
 Layer maintainers: Andrea Adami <andrea.adami at gmail.com>
                    Paul Eggleton <paul.eggleton at linux.intel.com>
diff --git a/meta-multimedia/README b/meta-multimedia/README
index 8412770..d82ceab 100644
--- a/meta-multimedia/README
+++ b/meta-multimedia/README
@@ -10,7 +10,8 @@ revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-multimedia][dylan]' in the subject'
 
-When sending single patches, please use something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-multimedia][dylan][PATCH
+When sending single patches, please use something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-multimedia][dylan][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.
 
diff --git a/meta-networking/MAINTAINERS b/meta-networking/MAINTAINERS
index 393f037..953e603 100644
--- a/meta-networking/MAINTAINERS
+++ b/meta-networking/MAINTAINERS
@@ -6,7 +6,7 @@ development mailing list (openembedded-devel at lists.openembedded.org) with
 
 When sending single patches, please use something like:
 
-   git send-email -1 \
+   git send-email -1 -M \
         --to openembedded-devel at lists.openembedded.org \
         --subject-prefix=meta-networking][PATCH
 
diff --git a/meta-oe/README b/meta-oe/README
index 0d6894c..267d5c4 100644
--- a/meta-oe/README
+++ b/meta-oe/README
@@ -6,7 +6,8 @@ revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-oe]' in the subject'
 
-When sending single patches, please use something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][dylan][PATCH'
+When sending single patches, please use something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][dylan][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.
 
diff --git a/meta-ruby/README b/meta-ruby/README
index 9ef9986..0d447a1 100644
--- a/meta-ruby/README
+++ b/meta-ruby/README
@@ -10,6 +10,7 @@ revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-ruby][dylan]' in the subject'
 
-When sending single patches, please using something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-ruby][dylan][PATCH'
+When sending single patches, please using something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-ruby][dylan][PATCH'
 
 Interim layer maintainer: Martin Jansa <Martin.Jansa at gmail.com>
diff --git a/meta-systemd/README b/meta-systemd/README
index 150a020..e31745e 100644
--- a/meta-systemd/README
+++ b/meta-systemd/README
@@ -17,7 +17,8 @@ $[LAYERDIR}/<layer name>/recipes-<group-name>/<recipe-name>/<recipe-name>.bbappe
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-oe][meta-systemd][dylan]' in the subject'
 
-When sending single patches, please use something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][meta-systemd][dylan][PATCH'
+When sending single patches, please use something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][meta-systemd][dylan][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.
 
diff --git a/meta-xfce/README b/meta-xfce/README
index 4963a24..2b79780 100644
--- a/meta-xfce/README
+++ b/meta-xfce/README
@@ -16,6 +16,7 @@ BBMASK = "meta-xfce/recipes-multimedia"
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-xfce][dylan]' in the subject'
 
-When sending single patches, please using something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-xfce][dylan][PATCH'
+When sending single patches, please using something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-xfce][dylan][PATCH'
 
 Interim layer maintainer: Andreas Müller <schnitzeltony at googlemail.com>
diff --git a/toolchain-layer/README b/toolchain-layer/README
index 5996b6c..1f9be50 100644
--- a/toolchain-layer/README
+++ b/toolchain-layer/README
@@ -6,7 +6,8 @@ revision: HEAD
 
 Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-oe][toolchain-layer]' in the subject'
 
-When sending single patches, please use something like 'git send-email -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer][PATCH'
+When sending single patches, please use something like:
+'git send-email -M -1 --to openembedded-devel at lists.openembedded.org --subject-prefix=meta-oe][toolchain-layer][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.

More information about the Openembedded-commits mailing list