Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1btW1t-0002oI-S8 for pgadmin-hackers@arkaria.postgresql.org; Mon, 10 Oct 2016 08:33:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1btW1t-0001a2-En for pgadmin-hackers@arkaria.postgresql.org; Mon, 10 Oct 2016 08:33:49 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1btW1s-0001XO-Gf for pgadmin-hackers@postgresql.org; Mon, 10 Oct 2016 08:33:48 +0000 Received: from mail-io0-x22c.google.com ([2607:f8b0:4001:c06::22c]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1btW1q-0001dp-4k for pgadmin-hackers@postgresql.org; Mon, 10 Oct 2016 08:33:47 +0000 Received: by mail-io0-x22c.google.com with SMTP id r30so103888580ioi.1 for ; Mon, 10 Oct 2016 01:33:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gs2XyyyQ582Vj6XDtZjgfJo/82ybf2wkIGS3pQM5PFE=; b=mvejkvcDXkzHczjh+VVjk72b4/nmfrxNWww6CCHmoieAY1YkmJnDY38WRbsb8vJU0A PC6/c9zkJmMSgf5IG75tJTmrYnEWuaPPmQpJK2/G8bQ7n6gOeUQ2vIVNoGmedtmota9u ucGpZFDAA7zl/iwvXQDTh9WOwEuO6wb6Roztl2FN8VECR7a/rcfoV+BcdbORlkr7fM0e HFvd2AvqigDb1h5TOAlFck0yUNKkegsbigHKxq+tPN3D8Lbwsd1HYZEskNSu3PC4Ca2T XfiYYhuoa4x+kGW5schW82cPNRjPIKMtRd2Bvy8re6yTDb5ds3fhJ98t94y4rB0WLsAD tEwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gs2XyyyQ582Vj6XDtZjgfJo/82ybf2wkIGS3pQM5PFE=; b=Rku9Ta9ohi2bsxo//DO3NFs1VnvSGiNhj7mKymjrlkebNb8SHs/nLXzc0DaVDecija 2cmrau2Wld/DVkFU4QX4UmMEI/ptDxPNpV9BUYfwc/Zel87HmeMvn6xlHw2Ul/yMZsCy iwrQPraNSzNHhf+ZACFZbxCSufrbYy/h1N+qFyZWchFoeUd9Ba2zRFxIxUbLvMu4Un1t XgGdTePn615MAay/P2ZKI+v3VsBUB7ACEj3dg3ZI+0Hj816NsIOpeHGFRlN2avuAnH/6 QAdrwSa566132Kao2mBUWAw2BfBc9BfTGJkOaVUg3lfhj8g8l6IeL6O+sdrLgm4eRU6W siRQ== X-Gm-Message-State: AA6/9Rm/RsyBDOywnfTHE+yiOcc+bWEZOQXbHiC1iA5g0iS4swaeQqF51/Cffdj84FSxcbpcKi2FKrnpJBAeDg== X-Received: by 10.107.11.98 with SMTP id v95mr32173621ioi.145.1476088425249; Mon, 10 Oct 2016 01:33:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.146.135 with HTTP; Mon, 10 Oct 2016 01:33:44 -0700 (PDT) In-Reply-To: <1476016037-17290-2-git-send-email-aklhfex@gmail.com> References: <1476016037-17290-1-git-send-email-aklhfex@gmail.com> <1476016037-17290-2-git-send-email-aklhfex@gmail.com> From: Dave Page Date: Mon, 10 Oct 2016 09:33:44 +0100 Message-ID: Subject: Re: [PATCH 2/2] Improve references to the mailing list in docs To: Chris Mayo Cc: "pgadmin-hackers@postgresql.org" Content-Type: multipart/alternative; boundary=001a113f91103e9edb053e7e9eff X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a113f91103e9edb053e7e9eff Content-Type: text/plain; charset=UTF-8 Thanks, patch applied. BTW, please send any future patches as attachments rather than inline, as I had to apply this manually as it got munged in the email body. Thanks! On Sunday, October 9, 2016, Chris Mayo wrote: > Just let Sphinx discover the email address; displays better in > browser and pgAdmin4 runtime. > > Signed-off-by: Chris Mayo > > --- > docs/en_US/contributions.rst | 2 +- > docs/en_US/submitting_patches.rst | 4 ++-- > 2 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/docs/en_US/contributions.rst b/docs/en_US/contributions.rst > index a395e12..7cd3026 100644 > --- a/docs/en_US/contributions.rst > +++ b/docs/en_US/contributions.rst > @@ -4,7 +4,7 @@ > pgAdmin Project Contributions > ***************************** > > -pgAdmin is an open-source project that invites you to get involved in the > development process. For more information about contributing to the > pgAdmin project, contact the developers on the pgAdmin mailing list pgadmin-hackers@postgresql.org > to discuss any ideas you > might have for enhancements or bug fixes. > +pgAdmin is an open-source project that invites you to get involved in the > development process. For more information about contributing to the > pgAdmin project, contact the developers on the pgAdmin mailing list > pgadmin-hackers@postgresql.org to discuss any ideas you > might have for enhancements or bug fixes. > > In the sections listed below, you'll find detailed information about the > development process used to develop, improve, and maintain the pgAdmin > client. > > diff --git a/docs/en_US/submitting_patches.rst b/docs/en_US/submitting_ > patches.rst > index 9f8ab42..a3ced06 100644 > --- a/docs/en_US/submitting_patches.rst > +++ b/docs/en_US/submitting_patches.rst > @@ -5,7 +5,7 @@ Submitting Patches > ****************** > > Before developing a patch for pgAdmin you should always contact the > developers > -on the `mailing list >` to discuss your > +on the mailing list pgadmin-hackers@postgresql.org to > discuss your > plans. This ensures that others know if you're fixing a bug and can then > avoid > duplicating your work, and in the case of large patches, gives the > community > the chance to discuss and refine your ideas before investing too much time > @@ -31,6 +31,6 @@ 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 >`. > Please ensure you > +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. > \ No newline at end of file > -- > 2.7.3 > > > > -- > Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org > ) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-hackers > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company --001a113f91103e9edb053e7e9eff Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks, patch applied.

BTW, please send any future patch= es as attachments rather than inline, as I had to apply this manually as it= got munged in the email body.

Thanks!

On= Sunday, October 9, 2016, Chris Mayo <aklhfex@gmail.com> wrote:
Just = let Sphinx discover the email address; displays better in
browser and pgAdmin4 runtime.

Signed-off-by: Chris Mayo <aklhfex@gmail.com> ---
=C2=A0docs/en_US/contributions.rst=C2=A0 =C2=A0 =C2=A0 | 2 +-
=C2=A0docs/en_US/submitting_patches.rst | 4 ++--
=C2=A02 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/en_US/contributions.rst b/docs/en_US/contributions.rst index a395e12..7cd3026 100644
--- a/docs/en_US/contributions.rst
+++ b/docs/en_US/contributions.rst
@@ -4,7 +4,7 @@
=C2=A0pgAdmin Project Contributions
=C2=A0*****************************

-pgAdmin is an open-source project that invites you to get involved in the = development process.=C2=A0 For more information about contributing to the p= gAdmin project, contact the developers on the pgAdmin mailing list <mail= to:pgadmin-hackers@postgresql.org> to = discuss any ideas you might have for enhancements or bug fixes.
+pgAdmin is an open-source project that invites you to get involved in the = development process.=C2=A0 For more information about contributing to the p= gAdmin project, contact the developers on the pgAdmin mailing list pgadmin-hackers@postgresql.org to discuss any id= eas you might have for enhancements or bug fixes.

=C2=A0In the sections listed below, you'll find detailed information ab= out the development process used to develop, improve, and maintain the pgAd= min client.

diff --git a/docs/en_US/submitting_patches.rst b/docs/en_US/submitting= _patches.rst
index 9f8ab42..a3ced06 100644
--- a/docs/en_US/submitting_patches.rst
+++ b/docs/en_US/submitting_patches.rst
@@ -5,7 +5,7 @@ Submitting Patches
=C2=A0******************

=C2=A0Before developing a patch for pgAdmin you should always contact the d= evelopers
-on the `mailing list <mailto:pgadmin-hack= ers@postgresql.org>` to discuss your
+on the mailing list pgadmin-hackers@postgres= ql.org to discuss your
=C2=A0plans. This ensures that others know if you're fixing a bug and c= an then avoid
=C2=A0duplicating your work, and in the case of large patches, gives the co= mmunity
=C2=A0the chance to discuss and refine your ideas before investing too much= time
@@ -31,6 +31,6 @@ to create a patch between your development branch and the= public master branch.
=C2=A0Once you have your patch, check it thoroughly to ensure it meets the = pgAdmin
=C2=A0:doc:`coding_standards`, and review it against the :doc:`code_review`= to minimise
=C2=A0the chances of it being rejected. Once you're happy with your wor= k, mail it to the
-`mailing list <mailto:pgadmin-hackers@pos= tgresql.org>`. Please ensure you
+mailing list pgadmin-hackers@postgresql.org<= /a>. Please ensure you
=C2=A0include a full description of what the patch does, as well as the rat= ionale for
=C2=A0any important design decisions.
\ No newline at end of file
--
2.7.3



--
Sent via pgadmin-hackers mailing list (pgadmi= n-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-hackers


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @= pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL= Company

--001a113f91103e9edb053e7e9eff--