|
296 | 296 |
|
297 | 297 | <para> |
298 | 298 | In general, send bug reports to the bug report mailing list at |
299 | | - <email>pgsql-bugs@postgresql.org</email>. |
| 299 | + <email>pgsql-bugs@lists.postgresql.org</email>. |
300 | 300 | You are requested to use a descriptive subject for your email |
301 | 301 | message, perhaps parts of the error message. |
302 | 302 | </para> |
|
306 | 306 | at the project's |
307 | 307 | <ulink url="https://www.postgresql.org/">web site</ulink>. |
308 | 308 | Entering a bug report this way causes it to be mailed to the |
309 | | - <email>pgsql-bugs@postgresql.org</email> mailing list. |
| 309 | + <email>pgsql-bugs@lists.postgresql.org</email> mailing list. |
310 | 310 | </para> |
311 | 311 |
|
312 | 312 | <para> |
|
318 | 318 |
|
319 | 319 | <para> |
320 | 320 | Do not send bug reports to any of the user mailing lists, such as |
321 | | - <email>pgsql-sql@postgresql.org</email> or |
322 | | - <email>pgsql-general@postgresql.org</email>. |
| 321 | + <email>pgsql-sql@lists.postgresql.org</email> or |
| 322 | + <email>pgsql-general@lists.postgresql.org</email>. |
323 | 323 | These mailing lists are for answering |
324 | 324 | user questions, and their subscribers normally do not wish to receive |
325 | 325 | bug reports. More importantly, they are unlikely to fix them. |
326 | 326 | </para> |
327 | 327 |
|
328 | 328 | <para> |
329 | 329 | Also, please do <emphasis>not</emphasis> send reports to |
330 | | - the developers' mailing list <email>pgsql-hackers@postgresql.org</email>. |
| 330 | + the developers' mailing list <email>pgsql-hackers@lists.postgresql.org</email>. |
331 | 331 | This list is for discussing the |
332 | 332 | development of <productname>PostgreSQL</productname>, and it would be nice |
333 | 333 | if we could keep the bug reports separate. We might choose to take up a |
|
337 | 337 |
|
338 | 338 | <para> |
339 | 339 | If you have a problem with the documentation, the best place to report it |
340 | | - is the documentation mailing list <email>pgsql-docs@postgresql.org</email>. |
| 340 | + is the documentation mailing list <email>pgsql-docs@lists.postgresql.org</email>. |
341 | 341 | Please be specific about what part of the documentation you are unhappy |
342 | 342 | with. |
343 | 343 | </para> |
344 | 344 |
|
345 | 345 | <para> |
346 | 346 | If your bug is a portability problem on a non-supported platform, |
347 | | - send mail to <email>pgsql-hackers@postgresql.org</email>, |
| 347 | + send mail to <email>pgsql-hackers@lists.postgresql.org</email>, |
348 | 348 | so we (and you) can work on |
349 | 349 | porting <productname>PostgreSQL</productname> to your platform. |
350 | 350 | </para> |
|
0 commit comments