various documentation, since those lists are now dead/deprecated.
Point to pgsql-bugs and/or pgsql-hackers as appropriate.
To try a manual configuration, look into the src/template directory
for a similar platform and use the '--with-template=' option.
-Please also contact <pgsql-ports@postgresql.org> to see about
+Please also contact <pgsql-bugs@postgresql.org> to see about
rectifying this. Include the above 'checking host system type...'
line.
*******************************************************************
To try a manual configuration, look into the src/template directory
for a similar platform and use the '--with-template=' option.
-Please also contact <pgsql-ports@postgresql.org> to see about
+Please also contact <pgsql-bugs@postgresql.org> to see about
rectifying this. Include the above 'checking host system type...'
line.
*******************************************************************
dnl Process this file with autoconf to produce a configure script.
-dnl $PostgreSQL: pgsql/configure.in,v 1.581 2009/01/06 15:38:44 tgl Exp $
+dnl $PostgreSQL: pgsql/configure.in,v 1.582 2009/01/06 17:27:06 tgl Exp $
dnl
dnl Developers, please strive to achieve this order:
dnl
To try a manual configuration, look into the src/template directory
for a similar platform and use the '--with-template=' option.
-Please also contact <pgsql-ports@postgresql.org> to see about
+Please also contact <pgsql-bugs@postgresql.org> to see about
rectifying this. Include the above 'checking host system type...'
line.
*******************************************************************
/*
- * $PostgreSQL: pgsql/contrib/pg_standby/pg_standby.c,v 1.16 2008/12/15 22:13:02 momjian Exp $
+ * $PostgreSQL: pgsql/contrib/pg_standby/pg_standby.c,v 1.17 2009/01/06 17:27:06 tgl Exp $
*
*
* pg_standby.c
* accessible directory. If you want to make other assumptions,
* such as using a vendor-specific archive and access API, these
* routines are the ones you'll need to change. You're
- * enouraged to submit any changes to pgsql-patches@postgresql.org
+ * enouraged to submit any changes to pgsql-hackers@postgresql.org
* or personally to the current maintainer. Those changes may be
* folded in to later versions of this program.
*/
-If PostgreSQL failed to compile on your computer or you found a bug that
-is likely to be specific to one platform, then please fill out this form
-and e-mail it to pgsql-ports@postgresql.org.
-
-To report non-porting-related bugs, fill out the form below and e-mail it to
-pgsql-bugs@postgresql.org.
+If PostgreSQL failed to compile on your computer or you found a bug,
+please fill out this form and e-mail it to pgsql-bugs@postgresql.org.
If your bug report has security implications and you'd prefer that it not
become immediately visible in public archives, don't send it to pgsql-bugs.
Security issues can be reported privately to security@postgresql.org.
If you not only found the problem but solved it and generated a patch
-then e-mail it to pgsql-patches@postgresql.org instead. Please use the
+then e-mail it to pgsql-hackers@postgresql.org instead. Please use the
command "diff -c" to generate the patch.
You may also enter a bug report at http://www.postgresql.org/ instead of
-<!-- $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.28 2007/01/31 20:56:18 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.29 2009/01/06 17:27:06 tgl Exp $ -->
<sect1 id="bug-reporting">
<title>Bug Reporting Guidelines</title>
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-ports@postgresql.org</email>,
+ send mail to <email>pgsql-hackers@postgresql.org</email>,
so we (and you) can work on
porting <productname>PostgreSQL</productname> to your platform.
</para>