database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-27 22:56:53 +03:00
Code

Fix typos.

Browse Source 
Robert Treat
This commit is contained in:
Bruce Momjian 2005-03-11 11:59:16 +00:00
parent e185618f5d
commit 85ecedf1d8
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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: Fri Mar 11 06:43:43 EST 2005 Last updated: Fri Mar 11 06:58:51 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)

12
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: Fri Mar 11 06:42:00 EST 2005</P> <P>Last updated: Fri Mar 11 06:58:51 EST 2005</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@ -199,7 +199,7 @@
<P><B>Basic system testing</B></P> <P><B>Basic system testing</B></P>
<P>The easiest way to test your code is to ensure that it builds <P>The easiest way to test your code is to ensure that it builds
against the latest verion of the code and that it does not generate against the latest version of the code and that it does not generate
compiler warnings.</P> compiler warnings.</P>
<P>It is worth advised that you pass --enable-cassert to <P>It is worth advised that you pass --enable-cassert to
@ -217,7 +217,7 @@
directory of the source tree. If any tests failure, directory of the source tree. If any tests failure,
investigate.</P> investigate.</P>
<P>If you've deliberately changed existing behaviour, this change <P>If you've deliberately changed existing behavior, this change
may cause a regression test failure but not any actual regression. may cause a regression test failure but not any actual regression.
If so, you should also patch the regression test suite.</P> If so, you should also patch the regression test suite.</P>
@ -479,7 +479,7 @@
<LI>The initscript;</LI> <LI>The initscript;</LI>
<LI>Any other ancilliary scripts and files;</LI> <LI>Any other ancillary scripts and files;</LI>
<LI>A README.rpm-dist document that tries to adequately document <LI>A README.rpm-dist document that tries to adequately document
both the differences between the RPM build and the WHY of the both the differences between the RPM build and the WHY of the
@ -608,7 +608,7 @@
cvs ... checkout pgsql cvs ... checkout pgsql
</PRE> </PRE>
<P>To get a past branch, you cd to whereever you want it and <P>To get a past branch, you cd to wherever you want it and
say</P> say</P>
<PRE> <PRE>
cvs ... checkout -r BRANCHNAME pgsql cvs ... checkout -r BRANCHNAME pgsql
@ -697,7 +697,7 @@
the source code is available at <A href= the source code is available at <A href=
"http://gborg.postgresql.org/project/pgweb/projdisplay.php">http://gborg.postgresql.org/project/pgweb/projdisplay.php</A> "http://gborg.postgresql.org/project/pgweb/projdisplay.php">http://gborg.postgresql.org/project/pgweb/projdisplay.php</A>
, the code for the next version of the website is under the , the code for the next version of the website is under the
"portal" module. You will al so find code for the "techdocs" "portal" module. You will also find code for the "techdocs"
website if you would like to contribute to that. A temporary todo website if you would like to contribute to that. A temporary todo
list for current website development issues is available at <A list for current website development issues is available at <A
href= href=