diff options
| author | antirez <antirez@gmail.com> | 2014-12-13 19:26:48 +0100 |
|---|---|---|
| committer | antirez <antirez@gmail.com> | 2014-12-13 19:26:48 +0100 |
| commit | c147cd848760c44791d73b03dbe2a4b8aa5b8c8e (patch) | |
| tree | f81da60698763bd8de04b3578b6824eb6a89d96f /CONTRIBUTING | |
| parent | d6410ed19a4930895f2591eed224d5ec5449393a (diff) | |
| download | redis-c147cd848760c44791d73b03dbe2a4b8aa5b8c8e.tar.gz | |
CONTRIBUTING updated.
Diffstat (limited to 'CONTRIBUTING')
| -rw-r--r-- | CONTRIBUTING | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/CONTRIBUTING b/CONTRIBUTING index f7b6836f7..b416b9561 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -20,7 +20,7 @@ each source file that you contribute. # How to provide a patch for a new feature -1. Drop a message to the Redis Google Group with a proposal of semantics/API. +1. If it is a major feature or a semantical change, write an RCP (Redis Change Proposal). Check the documentation here: https://github.com/redis/redis-rcp 2. If in step 1 you get an acknowledge from the project leaders, use the following procedure to submit a patch: @@ -31,4 +31,6 @@ each source file that you contribute. d. Initiate a pull request on github ( http://help.github.com/send-pull-requests/ ) e. Done :) +For minor fixes just open a pull request on Github. + Thanks! |