public inbox for [email protected]
help / color / mirror / Atom feedFrom: Chris Mayo <[email protected]>
To: [email protected]
Subject: [PATCH] Document that a patch should be submitted to the list as an attachment
Date: Mon, 10 Oct 2016 19:40:42 +0100
Message-ID: <[email protected]> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgadmin-hackers>
Signed-off-by: Chris Mayo <[email protected]>
---
docs/en_US/submitting_patches.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
Sent via pgadmin-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers
Attachments:
[text/x-patch] 0001-Document-that-a-patch-should-be-submitted-to-the-lis.patch (998B, 2-0001-Document-that-a-patch-should-be-submitted-to-the-lis.patch)
download | inline diff:
diff --git a/docs/en_US/submitting_patches.rst b/docs/en_US/submitting_patches.rst
index c077551..4ac878d 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 [email protected]. 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 [email protected].
+Please ensure you include a full description of what the patch does,
+as well as the rationale for any important design decisions.
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: [PATCH] Document that a patch should be submitted to the list as an attachment
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox