Skip to content

Commit d1ce4f7

Browse files
bmomjianbmomjian
committed
Add language about rights given by posting a patch:
 <li>PostgreSQL is licensed under a BSD license. By posting a patch to the public PostgreSQL mailling lists, you are giving the PostgreSQL Global Development Group the non-revokable right to distribute your patch under the BSD license. If you use code that is available under some other license that is BSD compatible (eg. public domain), please note that in your email submission.</li>
1 parent 2c6feff commit d1ce4f7

File tree

2 files changed

+25
-21
lines changed

2 files changed

+25
-21
lines changed

‎doc/FAQ_DEV

+12-10
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Tue Feb 27 18:12:31 EST 2007
4+
Last updated: Wed Feb 28 12:27:44 EST 2007
55

66
Current maintainer: Bruce Momjian (bruce@momjian.us)
77

@@ -136,20 +136,22 @@ General Questions
136136
src/tools/make_diff/difforig useful. (Unified diffs are only
137137
preferable if the file changes are single-line changes and do not
138138
rely on surrounding lines.)
139-
4. PostgreSQL is licensed under a BSD license, so any submissions
140-
must conform to the BSD license to be included. If you use code
141-
that is available under some other license that is BSD compatible
142-
(eg. public domain) please note that code in your email submission
139+
4. PostgreSQL is licensed under a BSD license. By posting a patch to
140+
the public PostgreSQL mailling lists, you are giving the
141+
PostgreSQL Global Development Group the non-revokable right to
142+
distribute your patch under the BSD license. If you use code that
143+
is available under some other license that is BSD compatible (eg.
144+
public domain), please note that in your email submission.
143145
5. Confirm that your changes can pass the regression tests. If your
144146
changes are port specific, please list the ports you have tested
145147
it on.
146-
6. Provide an implementation overview, preferably in code comments.
147-
Following the surrounding code commenting style is usually a good
148-
approach.
148+
6. If you are adding a new feature, confirm that it has been tested
149+
thoroughly. Try to test the feature in all conceivable scenarios.
149150
7. New feature patches should also be accompanied by documentation
150151
patches. If you need help checking the SQL standard, see 1.16.
151-
8. If you are adding a new feature, confirm that it has been tested
152-
thoroughly. Try to test the feature in all conceivable scenarios.
152+
8. Provide an implementation overview, preferably in code comments.
153+
Following the surrounding code commenting style is usually a good
154+
approach.
153155
9. If it is a performance patch, please provide confirming test
154156
results to show the benefit of your patch. It is OK to post
155157
patches without this information, though the patch will not be

‎doc/src/FAQ/FAQ_DEV.html

+13-11
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@
1313
<H1>Developer's Frequently Asked Questions (FAQ) for
1414
PostgreSQL</H1>
1515

16-
<P>Last updated: Tue Feb 27 18:12:31 EST 2007</P>
16+
<P>Last updated: Wed Feb 28 12:27:44 EST 2007</P>
1717

1818
<P>Current maintainer: Bruce Momjian (<A href=
1919
"mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
@@ -190,26 +190,28 @@ <H3 id="item1.5">1.5) I've developed a patch, what next?</H3>
190190
preferable if the file changes are single-line changes and do not
191191
rely on surrounding lines.)</li>
192192

193-
<li>PostgreSQL is licensed under a BSD license, so any submissions must
194-
conform to the BSD license to be included. If you use code that is
195-
available under some other license that is BSD compatible (eg. public
196-
domain) please note that code in your email submission</li>
193+
<li>PostgreSQL is licensed under a BSD license. By posting a patch
194+
to the public PostgreSQL mailling lists, you are giving the PostgreSQL
195+
Global Development Group the non-revokable right to distribute your
196+
patch under the BSD license. If you use code that is available under
197+
some other license that is BSD compatible (eg. public domain), please
198+
note that in your email submission.</li>
197199

198200
<li>Confirm that your changes can pass the regression tests. If your
199201
changes are port specific, please list the ports you have tested it
200202
on.</li>
201203

202-
<li>Provide an implementation overview, preferably in code comments.
203-
Following the surrounding code commenting style is usually a good
204-
approach.</li>
204+
<li>If you are adding a new feature, confirm that it has been tested
205+
thoroughly. Try to test the feature in all conceivable
206+
scenarios.</li>
205207

206208
<li>New feature patches should also be accompanied by documentation
207209
patches. If you need help checking the SQL standard, see <a href=
208210
"#item1.16">1.16</a>.</li>
209211

210-
<li>If you are adding a new feature, confirm that it has been tested
211-
thoroughly. Try to test the feature in all conceivable
212-
scenarios.</li>
212+
<li>Provide an implementation overview, preferably in code comments.
213+
Following the surrounding code commenting style is usually a good
214+
approach.</li>
213215

214216
<li>If it is a performance patch, please provide confirming test
215217
results to show the benefit of your patch. It is OK to post patches

0 commit comments

Comments
 (0)