summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWaldir Pimenta <waldir@email.com>2014-06-06 00:13:04 +0100
committerEdward Thomson <ethomson@microsoft.com>2014-10-24 20:17:54 -0400
commitac63149cd16e825d540da0e317fbba1f83d886bf (patch)
treec22b9264670e9d93bbb651e36b51eb852a4522e1
parentd09458f3e9f24afa0689ce90b7d4191872372634 (diff)
downloadlibgit2-ac63149cd16e825d540da0e317fbba1f83d886bf.tar.gz
Fix grammar of licensing sentence, add IRC links
Also various formatting, wrapping and capitalization tweaks.
-rw-r--r--CONTRIBUTING.md12
1 files changed, 7 insertions, 5 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8ebb99154..971c24566 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -15,7 +15,9 @@ from them into your own application.
## Discussion & Chat
-We hang out in the #libgit2 channel on irc.freenode.net.
+We hang out in the
+[`#libgit2`](http://webchat.freenode.net/?channels=#libgit2)) channel on
+irc.freenode.net.
Also, feel free to open an
[Issue](https://github.com/libgit2/libgit2/issues/new) to start a discussion
@@ -34,10 +36,10 @@ and when a critical bug fix needs to be backported, it will be done on a
First, know which version of libgit2 your problem is in and include it in
your bug report. This can either be a tag (e.g.
-[v0.17.0](https://github.com/libgit2/libgit2/releases/tag/v0.17.0) ) or a
-commit SHA (e.g.
-[01be7863](https://github.com/libgit2/libgit2/commit/01be786319238fd6507a08316d1c265c1a89407f)
-). Using [`git describe`](http://git-scm.com/docs/git-describe) is a
+[v0.17.0](https://github.com/libgit2/libgit2/releases/tag/v0.17.0)) or a
+commit SHA
+(e.g. [01be7863](https://github.com/libgit2/libgit2/commit/01be7863)).
+Using [`git describe`](http://git-scm.com/docs/git-describe) is a
great way to tell us what version you're working with.
If you're not running against the latest `master` branch version,