index 9f5d3cfdb6142e6208c5c9c13f8afdc7f1e98b3d..ee518fb9b6b39606d534fff3255e4e3646e002ee 100644 (file)
<para>
If you have installation problems on a platform that is known
to be supported according to recent build farm results, please report
- it to <email>pgsql-bugs@postgresql.org</email>. If you are interested
+ it to <email>pgsql-bugs@lists.postgresql.org</email>. If you are interested
in porting <productname>PostgreSQL</productname> to a new platform,
- <email>pgsql-hackers@postgresql.org</email> is the appropriate place
+ <email>pgsql-hackers@lists.postgresql.org</email> is the appropriate place
to discuss that.
</para>
</sect1>
index a6b5fe2b638731103ed07b33ac5f571f1e2ad8e0..02ed975ec2ffcec406eb907d54c9a08f94403c76 100644 (file)
<para>
In general, send bug reports to the bug report mailing list at
- <email>pgsql-bugs@postgresql.org</email>.
+ <email>pgsql-bugs@lists.postgresql.org</email>.
You are requested to use a descriptive subject for your email
message, perhaps parts of the error message.
</para>
at the project's
<ulink url="https://www.postgresql.org/">web site</ulink>.
Entering a bug report this way causes it to be mailed to the
- <email>pgsql-bugs@postgresql.org</email> mailing list.
+ <email>pgsql-bugs@lists.postgresql.org</email> mailing list.
</para>
<para>
<para>
Do not send bug reports to any of the user mailing lists, such as
- <email>pgsql-sql@postgresql.org</email> or
- <email>pgsql-general@postgresql.org</email>.
+ <email>pgsql-sql@lists.postgresql.org</email> or
+ <email>pgsql-general@lists.postgresql.org</email>.
These mailing lists are for answering
user questions, and their subscribers normally do not wish to receive
bug reports. More importantly, they are unlikely to fix them.
<para>
Also, please do <emphasis>not</emphasis> send reports to
- the developers' mailing list <email>pgsql-hackers@postgresql.org</email>.
+ the developers' mailing list <email>pgsql-hackers@lists.postgresql.org</email>.
This list is for discussing the
development of <productname>PostgreSQL</productname>, and it would be nice
if we could keep the bug reports separate. We might choose to take up a
<para>
If you have a problem with the documentation, the best place to report it
- is the documentation mailing list <email>pgsql-docs@postgresql.org</email>.
+ is the documentation mailing list <email>pgsql-docs@lists.postgresql.org</email>.
Please be specific about what part of the documentation you are unhappy
with.
</para>
<para>
If your bug is a portability problem on a non-supported platform,
- send mail to <email>pgsql-hackers@postgresql.org</email>,
+ send mail to <email>pgsql-hackers@lists.postgresql.org</email>,
so we (and you) can work on
porting <productname>PostgreSQL</productname> to your platform.
</para>
index 09a95041d6f76da53018bcd43525c206a89f1858..ae9c0c47c722fcfa05e6030419c49339874a50f5 100644 (file)
<xsl:param name="make.valid.html" select="1"></xsl:param>
<xsl:param name="generate.id.attributes" select="1"></xsl:param>
<xsl:param name="generate.legalnotice.link" select="1"></xsl:param>
-<xsl:param name="link.mailto.url">pgsql-docs@postgresql.org</xsl:param>
+<xsl:param name="link.mailto.url">pgsql-docs@lists.postgresql.org</xsl:param>
<xsl:param name="chunker.output.indent" select="'yes'"/>
<xsl:param name="chunk.quietly" select="1"></xsl:param>