diff options
author | IWASE Yusuke <iwase.yusuke0@gmail.com> | 2017-06-13 16:24:31 +0900 |
---|---|---|
committer | FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | 2017-06-22 16:07:49 +0900 |
commit | ef212fe87ef1ab78da71c5a237cedb0393657111 (patch) | |
tree | 4a85eefaea85b499ed02e7b1e7d9cbb71e4c223e | |
parent | cec1254a35bce38f8f5ca6de28aa055e2f1818e7 (diff) |
CONTRIBUTING: Update procedure for submitting patches
Signed-off-by: IWASE Yusuke <iwase.yusuke0@gmail.com>
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
-rw-r--r-- | CONTRIBUTING.rst | 18 |
1 files changed, 13 insertions, 5 deletions
diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index e301f1f0..2fc9493b 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -5,12 +5,20 @@ How to Get Your Change Into Ryu Submitting a change =================== -Send patches to ryu-devel@lists.sourceforge.net. Please don't use 'pull -request' on github. We expect you to send a patch in Linux kernel -development style. If you are not familiar with it, please read the -following document: +Send patches to ryu-devel@lists.sourceforge.net. Please don't use "Pull +Request" on GitHub. We expect you to send patches in "git-format-patch" +style. -https://www.kernel.org/doc/Documentation/SubmittingPatches +.. code-block:: bash + + # "N" means the number of commits to be included + $ git format-patch -s HEAD~N + + # To add cover (e.g., [PATCH 0/X]), specify "--cover-letter" option + $ git format-patch -s --cover-letter HEAD~N + + # You can send patches by "git send-email" command + $ git send-email --to="ryu-devel@lists.sourceforge.net" *.patch Please check your changes with pep8 and run unittests to make sure that they don't break the existing features. The following command |