database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-05 23:56:58 +03:00
Code

Typo fix from Brendan Jurd.

Browse Source
This commit is contained in:
Bruce Momjian 2007-09-23 18:06:47 +00:00
parent 33b9c8bd68
commit d16f270e59
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/FAQ_DEV
View File

@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Wed Aug 22 20:10:01 EDT 2007 Last updated: Sun Sep 23 14:06:36 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
@ -220,7 +220,7 @@ General Questions
The next step is to test your changes against the existing regression The next step is to test your changes against the existing regression
test suite. To do this, issue "make check" in the root directory of test suite. To do this, issue "make check" in the root directory of
the source tree. If any tests failure, investigate. the source tree. If any tests fail, investigate.
If you've deliberately changed existing behavior, this change might If you've deliberately changed existing behavior, this change might
cause a regression test failure but not any actual regression. If so, cause a regression test failure but not any actual regression. If so,

5
doc/src/FAQ/FAQ_DEV.html
View File

@ -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: Wed Aug 22 20:10:01 EDT 2007</P> <P>Last updated: Sun Sep 23 14:06:36 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>
@ -291,8 +291,7 @@
<P>The next step is to test your changes against the existing <P>The next step is to test your changes against the existing
regression test suite. To do this, issue "make check" in the root regression test suite. To do this, issue "make check" in the root
directory of the source tree. If any tests failure, directory of the source tree. If any tests fail, investigate.</P>
investigate.</P>
<P>If you've deliberately changed existing behavior, this change <P>If you've deliberately changed existing behavior, this change
might cause a regression test failure but not any actual regression. might cause a regression test failure but not any actual regression.