From c2cd2d3d3bca1232ec65e8d97a90596499e9d91e Mon Sep 17 00:00:00 2001 From: Chris Mayo Date: Tue, 11 Oct 2016 13:57:42 -0700 Subject: [PATCH] Clarify that patches should be sent as attachments. --- docs/en_US/submitting_patches.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en_US/submitting_patches.rst b/docs/en_US/submitting_patches.rst index c077551e4..4ac878d13 100644 --- a/docs/en_US/submitting_patches.rst +++ b/docs/en_US/submitting_patches.rst @@ -30,7 +30,7 @@ to create a patch between your development branch and the public master branch. Once you have your patch, check it thoroughly to ensure it meets the pgAdmin :doc:`coding_standards`, and review it against the :doc:`code_review` to minimise -the chances of it being rejected. Once you're happy with your work, mail it to the -mailing list pgadmin-hackers@postgresql.org. Please ensure you include a full -description of what the patch does, as well as the rationale for any important -design decisions. +the chances of it being rejected. Once you're happy with your work, mail it +as an attachment to the mailing list pgadmin-hackers@postgresql.org. +Please ensure you include a full description of what the patch does, +as well as the rationale for any important design decisions.