rapgenic/meta-raspberrypi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
5eb159d32d60780ee16c31d89fdbf77ffd6ab361
meta-raspberrypi/docs/contributing.md
Mirza Krak 34113350f4 docs: fix alignment of "code blocks" 
We provide a lot of variable examples as code blocks in the following
format:

	some text: `Variable`

or
	some test:
	`Variable`

Which is not as pretty as (when converted to html/pdf):

	some text:

		Variable

Converted all and hoppefully this will improve readability a bit.

Signed-off-by: Mirza Krak <mirza.krak@endian.se>
2017-05-26 12:16:52 +01:00

1.4 KiB
Raw Blame History

Contributing

Mailing list

The main communication tool we use is a mailing list:

Feel free to ask any kind of questions but always prepend your email subject with "[meta-raspberrypi]". This is because we use the 'yocto' mailing list and not a perticular 'meta-raspberrypi' mailing list.

Patches and pull requests

All the contributions should be compliant with the openembedded patch guidelines: http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

To contribute to this project you should send pull requests to the github mirror (https://github.com/agherzan/meta-raspberrypi). Additionally you can send the patches for review to the above specified mailing list.

When creating patches for the mailing list, please use something like:

git format-patch -s --subject-prefix='meta-raspberrypi][PATCH' origin

When sending patches to the mailing list, please use something like:

git send-email --to yocto@yoctoproject.org <generated patch>

Github issues

In order to manage and trace the meta-raspberrypi issues, we use github issues: https://github.com/agherzan/meta-raspberrypi/issues

If you push patches which have a github issue associated, please provide the issue number in the commit log just before "Signed-off-by" line(s). Example line for a bug: [Issue #13]