Update FAQ_DEV URL to output for text format.

REL8_3_STABLE
Bruce Momjian 19 years ago
parent 95e9f4ede3
commit 4dc6319331
  1. 6
      doc/FAQ_DEV
  2. 4
      doc/src/FAQ/FAQ_DEV.html

@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Thu May 31 20:28:04 EDT 2007 Last updated: Fri Jun 1 00:05:22 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
@ -149,7 +149,9 @@ General Questions
patches. If you need help checking the SQL standard, see 1.17. patches. If you need help checking the SQL standard, see 1.17.
8. Provide an implementation overview, preferably in code comments. 8. Provide an implementation overview, preferably in code comments.
Following the surrounding code commenting style is usually a good Following the surrounding code commenting style is usually a good
approach (also see this article). approach (also see this
http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=d
gr-FClnxw01linuxcodetips).
9. If it is a performance patch, please provide confirming test 9. If it is a performance patch, please provide confirming test
results to show the benefit of your patch. It is OK to post results to show the benefit of your patch. It is OK to post
patches without this information, though the patch will not be patches without this information, though the patch will not be

@ -13,7 +13,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for <H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1> PostgreSQL</H1>
<P>Last updated: Thu May 31 20:28:04 EDT 2007</P> <P>Last updated: Fri Jun 1 00:05:22 EDT 2007</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR> "mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
@ -209,7 +209,7 @@
<li>Provide an implementation overview, preferably in code comments. <li>Provide an implementation overview, preferably in code comments.
Following the surrounding code commenting style is usually a good Following the surrounding code commenting style is usually a good
approach (also see this <a approach (also see this <a
href="http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=dgr-FClnxw01linuxcodetips">article</a>).</li> href="http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=dgr-FClnxw01linuxcodetips">http://www.ibm.com/developerworks/linux/library/l-clear-code/?ca=dgr-FClnxw01linuxcodetips</a>).</li>
<li>If it is a performance patch, please provide confirming test <li>If it is a performance patch, please provide confirming test
results to show the benefit of your patch. It is OK to post patches results to show the benefit of your patch. It is OK to post patches

Loading…
Cancel
Save