docs: Format all links correctly

Signed-off-by: Paul Barker <pbarker@toganlabs.com>
This commit is contained in:
Paul Barker 2017-05-23 14:33:41 +01:00 committed by Andrei Gherzan
parent 5eb159d32d
commit 371f85ce53
2 changed files with 12 additions and 10 deletions

View File

@ -1,6 +1,6 @@
# meta-raspberrypi # meta-raspberrypi
Yocto BSP layer for the Raspberry Pi boards - http://www.raspberrypi.org/ . Yocto BSP layer for the Raspberry Pi boards - <http://www.raspberrypi.org/>.
[![Build Status](https://yocto-ci.resin.io/job/meta-raspberrypi1/badge/icon)](https://yocto-ci.resin.io/job/meta-raspberrypi1) [![Build Status](https://yocto-ci.resin.io/job/meta-raspberrypi1/badge/icon)](https://yocto-ci.resin.io/job/meta-raspberrypi1)
[![Build Status](https://yocto-ci.resin.io/job/meta-raspberrypi2/badge/icon)](https://yocto-ci.resin.io/job/meta-raspberrypi2) [![Build Status](https://yocto-ci.resin.io/job/meta-raspberrypi2/badge/icon)](https://yocto-ci.resin.io/job/meta-raspberrypi2)
@ -9,15 +9,17 @@ Yocto BSP layer for the Raspberry Pi boards - http://www.raspberrypi.org/ .
## Quick links ## Quick links
* Git repository web frontend: http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/ * Git repository web frontend:
* Mailing list (yocto mailing list): yocto@yoctoproject.org <http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/>
* Issues management (Github Issues): https://github.com/agherzan/meta-raspberrypi/issues * Mailing list (yocto mailing list): <yocto@yoctoproject.org>
* Issues management (Github Issues):
<https://github.com/agherzan/meta-raspberrypi/issues>
## Description ## Description
This is the general hardware specific BSP overlay for the RaspberryPi device. This is the general hardware specific BSP overlay for the RaspberryPi device.
More information can be found at: http://www.raspberrypi.org/ (Official Site) More information can be found at: <http://www.raspberrypi.org/> (Official Site)
The core BSP part of meta-raspberrypi should work with different The core BSP part of meta-raspberrypi should work with different
OpenEmbedded/Yocto distributions and layer stacks, such as: OpenEmbedded/Yocto distributions and layer stacks, such as:

View File

@ -3,8 +3,8 @@
## Mailing list ## Mailing list
The main communication tool we use is a mailing list: The main communication tool we use is a mailing list:
* yocto@yoctoproject.org * <yocto@yoctoproject.org>
* https://lists.yoctoproject.org/listinfo/yocto * <https://lists.yoctoproject.org/listinfo/yocto>
Feel free to ask any kind of questions but always prepend your email subject 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 with "[meta-raspberrypi]". This is because we use the 'yocto' mailing list and
@ -13,10 +13,10 @@ not a perticular 'meta-raspberrypi' mailing list.
## Patches and pull requests ## Patches and pull requests
All the contributions should be compliant with the openembedded patch All the contributions should be compliant with the openembedded patch
guidelines: http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines guidelines: <http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines>
To contribute to this project you should send pull requests to the github mirror To contribute to this project you should send pull requests to the github mirror
(https://github.com/agherzan/meta-raspberrypi). **Additionally** you can send (<https://github.com/agherzan/meta-raspberrypi>). **Additionally** you can send
the patches for review to the above specified mailing list. the patches for review to the above specified mailing list.
When creating patches for the mailing list, please use something like: When creating patches for the mailing list, please use something like:
@ -30,7 +30,7 @@ When sending patches to the mailing list, please use something like:
## Github issues ## Github issues
In order to manage and trace the meta-raspberrypi issues, we use github issues: In order to manage and trace the meta-raspberrypi issues, we use github issues:
https://github.com/agherzan/meta-raspberrypi/issues <https://github.com/agherzan/meta-raspberrypi/issues>
If you push patches which have a github issue associated, please provide the 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 issue number in the commit log just before "Signed-off-by" line(s). Example line