Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit179211a

Browse files
committed
Markup TODO as a URL.
1 parentd2f568d commit179211a

File tree

2 files changed

+19
-15
lines changed

2 files changed

+19
-15
lines changed

‎doc/FAQ

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Tue Nov 22 10:16:48 EST 2005
4+
Last updated: Tue Nov 22 10:21:51 EST 2005
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -194,15 +194,14 @@
194194
1.8) How do I submit a bug report?
195195

196196
Visit the PostgreSQL bug form at
197-
http://www.postgresql.org/support/submitbug.
198-
199-
Also check out our ftp site ftp://ftp.PostgreSQL.org/pub/ to see if
200-
there is a more recent PostgreSQL version.
197+
http://www.postgresql.org/support/submitbug. Also check out our ftp
198+
site ftp://ftp.PostgreSQL.org/pub/ to see if there is a more recent
199+
PostgreSQL version.
201200

202201
Bugs submitted using the bug form or posted to any PostgreSQL mailing
203202
list typically generates one of the following replies:
204203
* It is not a bug, and why
205-
* It is a known bug and isknownalready on the TODO list
204+
* It is a known bug and is already on the TODO list
206205
* The bug has been fixed in the current release
207206
* The bug has been fixed but is not packaged yet in an official
208207
release

‎doc/src/FAQ/FAQ.html

Lines changed: 14 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
alink="#0000ff">
1111
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1212

13-
<P>Last updated: Tue Nov 22 10:16:48 EST 2005</P>
13+
<P>Last updated: Tue Nov 22 10:21:51 EST 2005</P>
1414

1515
<P>Current maintainer: Bruce Momjian (<Ahref=
1616
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@@ -247,17 +247,17 @@ <H3 id="item1.8">1.8) How do I submit a bug report?</H3>
247247

248248
<P>Visit the PostgreSQL bug form at<Ahref=
249249
"http://www.postgresql.org/support/submitbug">
250-
http://www.postgresql.org/support/submitbug</A>.</P>
251-
252-
<P>Also check out our ftp site<Ahref=
250+
http://www.postgresql.org/support/submitbug</A>.
251+
Also check out our ftp site<Ahref=
253252
"ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/</A> to
254253
see if there is a more recent PostgreSQL version.</P>
255254

256255
<P>Bugs submitted using the bug form or posted to any PostgreSQL mailing
257256
list typically generates one of the following replies:</P>
258257
<ul>
259258
<li>It is not a bug, and why</li>
260-
<li>It is a known bug and is known already on the TODO list</li>
259+
<li>It is a known bug and is already on the
260+
<Ahref="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> list</li>
261261
<li>The bug has been fixed in the current release</li>
262262
<li>The bug has been fixed but is not packaged yet in an official
263263
release</li>
@@ -275,7 +275,8 @@ <H3 id="item1.8">1.8) How do I submit a bug report?</H3>
275275
<li>A patch has been created and will be included in the next major
276276
or minor release</li>
277277
<li>The bug cannot be fixed immediately and is added
278-
to the TODO list</li>
278+
to the<Ahref="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A>
279+
list</li>
279280
</ul>
280281
</li>
281282
</ul>
@@ -290,7 +291,9 @@ <H3 id="item1.9">1.9) How do I find out about known bugs or
290291
<P>A feature request usually results in one of the following
291292
replies:</P>
292293
<ul>
293-
<li>The feature is already on the TODO list</li>
294+
<li>The feature is already on the
295+
<Ahref="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A>
296+
list</li>
294297
<li>The feature is not desired because:
295298
<ul>
296299
<li>It duplicates existing functionality that already
@@ -300,11 +303,13 @@ <H3 id="item1.9">1.9) How do I find out about known bugs or
300303
<li>The feature would be insecure or unreliable</li>
301304
</ul>
302305
</li>
303-
<li>The new feature is added to the TODO list</li>
306+
<li>The new feature is added to the
307+
<Ahref="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A> list</li>
304308
</ul>
305309

306310
<P>PostgreSQL does not use a bug tracking system because we find
307-
it more efficient to respond directly to email and keep the TODO
311+
it more efficient to respond directly to email and keep the
312+
<Ahref="http://www.postgresql.org/docs/faqs.TODO.html">TODO</A>
308313
list up-to-date. In practice, bugs don't last very long in the
309314
software, and bugs that affect a large number of users are fixed
310315
rapidly. The only single place to find all changes, improvements,

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp