mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix wording, per Neil.

Browse Source
This commit is contained in:
Bruce Momjian 2006-08-12 03:48:32 +00:00
parent 7a3e30e608
commit aeb056f610
2 changed files with 5 additions and 26 deletions

27
doc/FAQ_DEV

@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Fri Aug 11 15:18:31 EDT 2006
Last updated: Fri Aug 11 23:48:27 EDT 2006
Current maintainer: Bruce Momjian (bruce@momjian.us)
@ -141,7 +141,7 @@ General Questions
7. New feature patches should also be accompanied by documentation
patches. If you need help checking the SQL standard, see 1.16.
8. If you are adding a new feature, confirm that it has been tested
thoughly. Try to test the feature in all conceivable scenarios.
thoroughly. Try to test the feature in all conceivable scenarios.
9. If it is a performance patch, please provide confirming test
results to show the benefit of your patch. It is OK to post
patches without this information, though the patch will not be
@ -292,28 +292,7 @@ General Questions
or
(add-hook 'c-mode-hook
(function
(lambda nil
(if (string-match "pgsql" buffer-file-name)
(progn
(c-set-style "bsd")
(setq c-basic-offset 4)
(setq tab-width(add-hook 'c-mode-hook
(function
(lambda nil
(if (string-match "pgsql" buffer-file-name)
(progn
(c-set-style "bsd")
(setq c-basic-offset 4)
(setq tab-width(add-hook 'c-mode-hook
(function
(lambda nil
(if (string-match "pgsql" buffer-file-name)
(progn
(c-set-style "bsd")
(setq c-basic-offset 4)
(setq tab-width (c-add-style "pgsql"
(c-add-style "pgsql"
'("bsd"
(indent-tabs-mode . t)
(c-basic-offset . 4)

4
doc/src/FAQ/FAQ_DEV.html

@ -13,7 +13,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1>
<P>Last updated: Fri Aug 11 15:15:40 EDT 2006</P>
<P>Last updated: Fri Aug 11 23:48:27 EDT 2006</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
@ -199,7 +199,7 @@
"#1.16">1.16</a>.</li>
<li>If you are adding a new feature, confirm that it has been tested
thoughly. Try to test the feature in all conceivable
thoroughly. Try to test the feature in all conceivable
scenarios.</li>
<li>If it is a performance patch, please provide confirming test