Version is now 2.5.1, first unstable release of Redis 2.6

[redis.git] / CONTRIBUTING

diff --git a/CONTRIBUTING b/CONTRIBUTING
index 644b599112ab7f334e1bb71223f80addda9a1f3c..623c5a6ec07b8bd5ad7da44b12ea173af54ead45 100644 (file)
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -1,13 +1,13 @@
-1. Enter irc.freenode.org #redis and start talking with 'antirez' and/or 'pietern' to check if there is interest for such a feature and to understand the probability of it being merged. We'll try hard to keep Redis simple... so you'll likely encounter an high resistence.
+1. Enter irc.freenode.org #redis and start talking with 'antirez' and/or 'pietern' to check if there is interest for such a feature and to understand the probability of it being merged. We'll try hard to keep Redis simple... so you'll likely encounter high resistance.

 
 2. Drop a message to the Redis Google Group with a proposal of semantics/API.
 
 3. If steps 1 and 2 are ok, use the following procedure to submit a patch:
 
 
 2. Drop a message to the Redis Google Group with a proposal of semantics/API.
 
 3. If steps 1 and 2 are ok, use the following procedure to submit a patch:
 

-    a. Fork Redis on github
+    a. Fork Redis on github ( http://help.github.com/fork-a-repo/ )

     b. Create a topic branch (git checkout -b my_branch)
     c. Push to your branch (git push origin my_branch)
     b. Create a topic branch (git checkout -b my_branch)
     c. Push to your branch (git push origin my_branch)

-    d. Create an issue in the Redis google code site with a link to your patch
+    d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ )

     e. Done :)
 
 Thanks!
     e. Done :)
 
 Thanks!