aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>1998-05-22 04:20:53 +0000
committerBruce Momjian <bruce@momjian.us>1998-05-22 04:20:53 +0000
commit9af6bd9962971d0e6f4cbec51852ecc734b21167 (patch)
tree395e453c3c9c2f9abe73a0974210fb2febe1223b
parent9f3d63936b0e155f71a020dc0255c323b9e67c2a (diff)
downloadpostgresql-9af6bd9962971d0e6f4cbec51852ecc734b21167.tar.gz
postgresql-9af6bd9962971d0e6f4cbec51852ecc734b21167.zip
Move FAQ_DEV to docs directory, where it belongs.
-rw-r--r--doc/FAQ_DEV (renamed from src/tools/FAQ_DEV)23
-rw-r--r--src/DEVELOPERS4
2 files changed, 15 insertions, 12 deletions
diff --git a/src/tools/FAQ_DEV b/doc/FAQ_DEV
index 72de67a988d..e9f663f5113 100644
--- a/src/tools/FAQ_DEV
+++ b/doc/FAQ_DEV
@@ -23,9 +23,9 @@ Questions answered:
1) What tools are available for developers?
-Aside from the User documentation mentioned in the regular FAQ, there are
-several development tools available. First, all the files in the /tools
-directory are designed for developers.
+Aside from the User documentation mentioned in the regular FAQ, there
+are several development tools available. First, all the files in the
+pgsql/src/tools directory are designed for developers.
RELEASE_CHANGES changes we have to make for each release
SQL_keywords standard SQL'92 keywords
@@ -42,14 +42,15 @@ directory are designed for developers.
mkldexport create AIX exports file
pgindent indents C source files
-Let me note some of these. If you point your browser at the tools/backend
-directory, you will see all the backend components in a flow chart. You can
-click on any one to see a description. If you then click on the directory
-name, you will be taken to the source directory, to browse the actual source
-code behind it. We also have several README files in some source directories
-to describe the function of the module. The browser will display these when
-you enter the directory also. The tools/backend directory is also contained
-on our web page under the title Backend Flowchart.
+Let me note some of these. If you point your browser at the
+pgsql/src/tools/backend directory, you will see all the backend
+components in a flow chart. You can click on any one to see a
+description. If you then click on the directory name, you will be taken
+to the source directory, to browse the actual source code behind it. We
+also have several README files in some source directories to describe
+the function of the module. The browser will display these when you
+enter the directory also. The pgsql/src/tools/backend directory is also
+contained on our web page under the title Backend Flowchart.
Second, you really should have an editor that can handle tags, so you can
tag a function call to see the function definition, and then tag inside that
diff --git a/src/DEVELOPERS b/src/DEVELOPERS
index 99f0c8c8908..ae44a31334f 100644
--- a/src/DEVELOPERS
+++ b/src/DEVELOPERS
@@ -1 +1,3 @@
-All the developer tools are located in the /tools directory.
+Read the Developer's FAQ in pgsql/doc/FAQ_DEV. All the developer tools
+are located in the pgsql/src/tools directory.
+