File tree 2 files changed +4
-4
lines changed
2 files changed +4
-4
lines changed Original file line number Diff line number Diff line change 1
1
2
2
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
3
3
4
- Last updated: Sat Dec 24 13:36:54 EST 2005
4
+ Last updated: Sat Dec 24 14:29:33 EST 2005
5
5
6
6
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
7
7
@@ -111,7 +111,7 @@ General Questions
111
111
Generate the patch in contextual diff format. If you are unfamiliar
112
112
with this, you might find the script src/tools/makediff/difforig
113
113
useful. Unified diffs are only preferrable if the file changes are
114
- single-line changes and do not rely on the surrouding lines.
114
+ single-line changes and do not rely on the surrounding lines.
115
115
116
116
Ensure that your patch is generated against the most recent version of
117
117
the code. If it is a patch adding new functionality, the most recent
Original file line number Diff line number Diff line change 13
13
< H1 > Developer's Frequently Asked Questions (FAQ) for
14
14
PostgreSQL</ H1 >
15
15
16
- < P > Last updated: Sat Dec 24 13:36:54 EST 2005</ P >
16
+ < P > Last updated: Sat Dec 24 14:29:33 EST 2005</ P >
17
17
18
18
< P > Current maintainer: Bruce Momjian (< A href =
19
19
"mailto:pgman@candle.pha.pa.us "> pgman@candle.pha.pa.us</ A > )< BR >
@@ -160,7 +160,7 @@ <H3 id="item1.5">1.5) I've developed a patch, what next?</H3>
160
160
unfamiliar with this, you might find the script
161
161
< I > src/tools/makediff/difforig</ I > useful. Unified diffs are
162
162
only preferrable if the file changes are single-line changes and
163
- do not rely on the surrouding lines.</ P >
163
+ do not rely on the surrounding lines.</ P >
164
164
165
165
< P > Ensure that your patch is generated against the most recent
166
166
version of the code. If it is a patch adding new functionality, the
You can’t perform that action at this time.
0 commit comments