summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPavel Grunt <pgrunt@redhat.com>2016-08-16 14:42:43 +0200
committerPavel Grunt <pgrunt@redhat.com>2016-08-16 14:42:43 +0200
commit0a547548cce3507577803593686535ebe9b46816 (patch)
tree71ef0c5aa3e98ea65542f8345e18243fbc65a5c7
parent6221056f12ab033dfc2e9fd957f7b115d3c189ce (diff)
developers: Recommend git send-email
-rw-r--r--content/pages/developers.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/content/pages/developers.rst b/content/pages/developers.rst
index 8c01150..1d3b808 100644
--- a/content/pages/developers.rst
+++ b/content/pages/developers.rst
@@ -50,8 +50,8 @@ that your patch will get rejected.
Like to send a patch?
+++++++++++++++++++++
-Before sending a patch to spice-devel@lists.freedesktop.org make sure that it
-follows these guidelines:
+Before sending a patch to spice-devel@lists.freedesktop.org using **git send-email**
+make sure that it follows these guidelines:
- It applies and compiles correctly with the latest development version
- The code adheres to Spice coding convention and style as specified in `Spice
@@ -61,7 +61,7 @@ follows these guidelines:
patch. Make sure applying each patch does not break the build
- Write clear and meaningful description and explanation in the commit message
- Be as responsive as possible to the review comments
-- The patch was prepared using git format-patch
+- The patch was prepared using **git format-patch**
- The patch successfully compiles on all supported platforms
Like to send a patch but don't have time for all the “nonsense”?