[oe] [meta-qt5 PATCH] README: Rework to start using GitHub for development

[Martin Jansa]

On Fri, Jun 22, 2018 at 03:32:46PM -0300, Otavio Salvador wrote:
> This changes the content so we start sending people to GitHub and
> deprecate the OpenEmbedded-Devel mailing list as the place for patch
> submission.
> 
> The content has been reworked so it renders better inside GitHub and
> provide a more structured content.

I'm done with patchwork.

If anyone has some pending changes which I haven't merged to master-next
last night, then send pings or re-submit them as pull-requests. Pending
changes from master-next will be merged to master together with 5.11.1
upgrade soon.

Acked-by: Martin Jansa <Martin.Jansa at gmail.com>
 
> Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>
> ---
> 
>  README    | 33 ---------------------------------
>  README.md | 32 ++++++++++++++++++++++++++++++++
>  2 files changed, 32 insertions(+), 33 deletions(-)
>  delete mode 100644 README
>  create mode 100644 README.md
> 
> diff --git a/README b/README
> deleted file mode 100644
> index 9817851..0000000
> --- a/README
> +++ /dev/null
> @@ -1,33 +0,0 @@
> -This layer depends on:
> -
> -URI: git://github.com/openembedded/oe-core.git
> -branch: master
> -revision: HEAD
> -
> -When building stuff like qtdeclarative, qtquick, qtwebkit, make sure that
> -you have required PACKAGECONFIG options enabled in qtbase build, see qtbase.inc
> -for detail.
> -
> -Send pull requests to openembedded-devel at lists.openembedded.org with '[meta-qt5]' 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-qt5][PATCH'
> -
> -Change option '-1' to '-n' for n number of patches in series
> -
> -You are encouraged to fork the mirror on github[1] to share your
> -patches. This is preferred for patch sets consisting of more than one
> -patch. Other services like gitlab, 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.
> -
> -1. https://github.com/meta-qt5/meta-qt5/
> -
> -meta-qt5 has Yocto Project Compatible status since 2013:
> -https://www.yoctoproject.org/product/meta-qt5
> -
> -Main layer maintainers:
> -  Martin 'JaMa' Jansa <martin.jansa at gmail.com>
> -  Otavio Salvador <otavio at ossystems.com.br>
> diff --git a/README.md b/README.md
> new file mode 100644
> index 0000000..fe94321
> --- /dev/null
> +++ b/README.md
> @@ -0,0 +1,32 @@
> +Qt5 OpenEmbedded/Yocto Project layer
> +====================================
> +
> +This layer depends on:
> +
> +URI: https://github.com/openembedded/openembedded-core
> +branch: master
> +revision: HEAD
> +
> +When building stuff like `qtdeclarative`, `qtquick`, `qtwebkit`, make
> +sure that you have required `PACKAGECONFIG` options enabled in qtbase
> +build, see `qtbase` recipe for detail.
> +
> +
> +Contributing
> +------------
> +
> +Please submit any patches against the `meta-qt5` layer by using the
> +GitHub pull-request feature.  Fork the repo, make a branch, do the
> +work, rebase from upstream, create the pull request, yada-yada.
> +
> +Maintainers
> +-----------
> +
> +- Martin 'JaMa' Jansa <martin.jansa at gmail.com>
> +- Otavio Salvador <otavio at ossystems.com.br>
> +
> +Yocto Project Compatible
> +------------------------
> +
> +meta-qt5 has Yocto Project Compatible status since 2013:
> +https://www.yoctoproject.org/product/meta-qt5
> -- 
> 2.17.1
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20180622/56495a58/attachment-0002.sig>