Mention the linux-nfc mailing list for contributions and current repositories - GitHub and kernel.org. Document explicitly that contributions can come also via GitHub pull request. For many developers without experience in development of Linux kernel, the GitHub PRs are easier than the patch-email workflow. Signed-off-by: Krzysztof Kozlowski --- README | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/README b/README index 8204b690eda0..509363bccac3 100644 --- a/README +++ b/README @@ -54,3 +54,21 @@ disabled with the following configuration options: Running ./bootstrap-configure will build the configure script and then run it, with maintainer mode enabled. bootstrap-configure will configure neard with all features enabled. + +Bugs and contributing +===================== + +Please send bug reports to mailing list: + linux-nfc(a)lists.01.org + +The project development happens on GitHub: + https://github.com/linux-nfc/neard + +However for historical reasons the releases are also mirrored on kernel.org +repository: + https://git.kernel.org/pub/scm/network/nfc/neard.git/ + +Contributions can come in a form of patches sent to linux-nfc(a)lists.01.org or +GitHub pull requests on mentioned GitHub repository. + +See also HACKING and doc/coding-style.txt files. -- 2.30.2