]>
Commit | Line | Data |
---|---|---|
8e30092f | 1 | Note: by contributing code to the Redis project in any form, including sending |
2 | a pull request via Github, a code fragment or patch via private email or | |
3 | public discussion groups, you agree to release your code under the terms | |
4 | of the BSD license that you can find in the COPYING file included in the Redis | |
5 | source distribution. | |
6 | ||
f4eb4b33 | 7 | # IMPORTANT: HOW TO USE REDIS GITHUB ISSUES |
30d31cc8 | 8 | |
f4eb4b33 | 9 | * Github issues SHOULD ONLY BE USED to report bugs, and for DETAILED feature |
10 | requests. Everything else belongs to the Redis Google Group. | |
30d31cc8 | 11 | |
f4eb4b33 | 12 | PLEASE DO NOT POST GENERAL QUESTIONS that are not about bugs or suspected |
13 | bugs in the Github issues system. We'll be very happy to help you and provide | |
14 | all the support in the Redis Google Group. | |
15 | ||
16 | Redis Google Group address: | |
17 | ||
18 | https://groups.google.com/forum/?fromgroups#!forum/redis-db | |
19 | ||
20 | # How to provide a patch for a new feature | |
21 | ||
22 | 1. Drop a message to the Redis Google Group with a proposal of semantics/API. | |
23 | ||
24 | 2. If in steps 1 you get an acknowledge from the project leaders, use the | |
25 | following procedure to submit a patch: | |
30d31cc8 | 26 | |
e491a1a1 | 27 | a. Fork Redis on github ( http://help.github.com/fork-a-repo/ ) |
30d31cc8 | 28 | b. Create a topic branch (git checkout -b my_branch) |
29 | c. Push to your branch (git push origin my_branch) | |
e491a1a1 | 30 | d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ ) |
30d31cc8 | 31 | e. Done :) |
32 | ||
33 | Thanks! |