...
 
Commits (2)
......@@ -2,7 +2,7 @@ Hacking
=======
This document describes how to start hacking on the libjaylink project.
Make sure you read through the README file before continuing.
Make sure you read through the README.md file before continuing.
Coding style
......@@ -28,7 +28,7 @@ project:
- Push your changes to a public Git repository and send the URL where to pull
them from.
In any case, send directly to <jaylink-dev@marcschink.de>.
In any case, send directly to <dev@zapb.de>.
Before submitting, please consider the following:
- Every single patch must be compilable.
......@@ -42,7 +42,7 @@ Before submitting, please consider the following:
Bug reports
-----------
Send bug reports directly to <jaylink-dev@marcschink.de>.
Send bug reports directly to <dev@zapb.de>.
Please try to include all of the following information in your report:
- Instructions to reproduce the bug (e.g., command-line invocations)
......
......@@ -27,7 +27,7 @@ AC_CONFIG_AUX_DIR([build-aux])
AC_CANONICAL_HOST
AM_INIT_AUTOMAKE([-Wall -Werror])
AM_INIT_AUTOMAKE([foreign -Wall -Werror])
# Enable additional compiler warnings via -Wall and -Wextra. Use hidden
# visibility for all non-static symbols by default with -fvisibility=hidden.
......