README: fix typo
Without this change, 'git send-email' complains of a missing argument. Tested with git 1.7.7.6 on Fedora 16.
--- meta-oe/README | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
meta-oe/README +1 -1
@@ -6,7 +6,7 @@ revision: HEAD Send pull requests to [email protected] with '[meta-oe]' in the subject' -When sending single patches, please use something like 'git send-email -1 --to [email protected] --subject-prefix meta-oe' +When sending single patches, please use something like 'git send-email -1 --to [email protected] --subject-prefix=meta-oe' 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.
Signature · 1 line
1.7.7.6
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 08-03-12 16:14, Gary Thomas schreef:
Quoted 1 line
Without this change, 'git send-email' complains of a missing argument.
Only if there's a dir called 'meta-oe', git is weird like that.
regards,
Koen
Quoted 18 lines
Tested with git 1.7.7.6 on Fedora 16.
Signed-off-by Gary Thomas <[email protected]> --- meta-oe/README | 2+- 1 files changed, 1 insertions(+), 1 deletions(-)
meta-oe/README index a195919..ed14866 renamed from meta-oe/README +0
-0100644 --- a/meta-oe/README +++ b/meta-oe/README @@ -6,7 +6,7 @@
revision: HEADSend pull requests to [email protected] with '[meta-oe]' in the subject'
-When sending single patches, please use something like 'git send-email -1 --to [email protected] --subject-prefix meta-oe' +When sending single patches, please use something like 'git send-email -1 --to [email protected] --subject-prefix=meta-oe'
Quoted 8 lines
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk9ZqQ8ACgkQMkyGM64RGpEqIACdGmcFzw6kCjxJm1sRPOXsNUr3 ygkAnRVRraA/+17ijY+91QpYk79VrMV8
=DHsY
-----END PGP SIGNATURE-----