aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarc Schink <dev@zapb.de>2020-05-31 13:48:22 +0200
committerMarc Schink <dev@zapb.de>2020-05-31 13:48:22 +0200
commita305df2881562fe5edf93c40cbe02b47b2ccea2c (patch)
tree13be77a5c85ff326911b36d992f9039721efdcbe
parent336e297bb582dd49aa72ca6926e1ecfafe52e3d1 (diff)
downloadlibjaylink-a305df2881562fe5edf93c40cbe02b47b2ccea2c.zip
libjaylink-a305df2881562fe5edf93c40cbe02b47b2ccea2c.tar.gz
libjaylink-a305df2881562fe5edf93c40cbe02b47b2ccea2c.tar.bz2
HACKING: Some small updates
Signed-off-by: Marc Schink <dev@zapb.de>
-rw-r--r--HACKING6
1 files changed, 3 insertions, 3 deletions
diff --git a/HACKING b/HACKING
index a654e2a..0175378 100644
--- a/HACKING
+++ b/HACKING
@@ -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)