12345678910111213141516171819202122232425262728293031323334 |
- Note: by contributing code to the Redis project in any form, including sending
- a pull request via Github, a code fragment or patch via private email or
- public discussion groups, you agree to release your code under the terms
- of the BSD license that you can find in the COPYING file included in the Redis
- source distribution. You will include BSD license in the COPYING file within
- each source file that you contribute.
- # IMPORTANT: HOW TO USE REDIS GITHUB ISSUES
- * Github issues SHOULD ONLY BE USED to report bugs, and for DETAILED feature
- requests. Everything else belongs to the Redis Google Group.
- PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected
- bugs in the Github issues system. We'll be very happy to help you and provide
- all the support in the Redis Google Group.
- Redis Google Group address:
-
- https://groups.google.com/forum/?fromgroups#!forum/redis-db
- # How to provide a patch for a new feature
- 1. Drop a message to the Redis Google Group with a proposal of semantics/API.
- 2. If in step 1 you get an acknowledge from the project leaders, use the
- following procedure to submit a patch:
- 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)
- d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ )
- e. Done :)
- Thanks!
|