summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--README11
1 files changed, 6 insertions, 5 deletions
diff --git a/README b/README
index 17f8273..4c2d762 100644
--- a/README
+++ b/README
@@ -320,11 +320,12 @@ Feel free to ask any kind of questions but always prepend your email subject
320with "[meta-raspberrypi]". This is because we use the 'yocto' mailing list and 320with "[meta-raspberrypi]". This is because we use the 'yocto' mailing list and
321not a perticular 'meta-raspberrypi' mailing list. 321not a perticular 'meta-raspberrypi' mailing list.
322 322
323To contribute to this layer you should send the patches for review to the 3237.B. Patches and pull requests
324above specified mailing list. 324==============================
325The patches should be compliant with the openembedded patch guidelines:
326http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
327 325
326To contribute to this project you should send pull requests to the github mirror
327(<https://github.com/agherzan/meta-raspberrypi>). **Additionally** you can send
328the patches for review to the above specified mailing list.
328 329
329When creating patches, please use something like: 330When creating patches, please use something like:
330 331
@@ -334,7 +335,7 @@ When sending patches to mailing list, please use something like:
334 335
335 git send-email --to yocto@yoctoproject.org <generated patch> 336 git send-email --to yocto@yoctoproject.org <generated patch>
336 337
3377.B. Github issues 3387.C. Github issues
338================== 339==================
339In order to manage and trace the meta-raspberrypi issues, we use github issues: 340In order to manage and trace the meta-raspberrypi issues, we use github issues:
340 https://github.com/agherzan/meta-raspberrypi/issues 341 https://github.com/agherzan/meta-raspberrypi/issues