summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorSean V Kelley <seanvk@posteo.de>2017-01-26 15:10:19 -0800
committerSean V Kelley <seanvk@posteo.de>2017-01-26 15:10:19 -0800
commit090d8d6c4283797103b3675ab867b53769d83edd (patch)
tree1877a9174bc5b9f97f5944f1fa40db90d0ac7da7 /CONTRIBUTING.md
parentbd6a786ff2001debe2f75b7a163b3aae9f16697a (diff)
downloadlibva-intel-driver-090d8d6c4283797103b3675ab867b53769d83edd.tar.gz
github: Updated mailing list
Also corrected link to filing new issues. Signed-off-by: Sean V Kelley <seanvk@posteo.de>
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0ff0e647..b1f06060 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -48,11 +48,11 @@ Once you've finished making your changes push them to your fork and send the PR
If you have a problem, please let us know. IRC is a perfectly fine place
to quickly informally bring something up, if you get a response. The
-[mailing list](http://lists.freedesktop.org/mailman/listinfo/libva)
+[mailing list](https://lists.01.org/mailman/listinfo/intel-vaapi-media)
is a more durable communication channel.
If it's a bug not already documented, by all means please [open an
-issue in github](https://github.com/01org/libva/issues/new) so we all get visibility
+issue in github](https://github.com/01org/intel-vaapi-driver/issues/new) so we all get visibility
to the problem and can work towards a resolution.
For feature requests we're also using github issues, with the label