@@ -76,6 +76,7 @@ <H3><A name="1">1</A>) What tools are available for
7676 make_mkid make mkid ID files
7777 mkldexport create AIX exports file
7878 pgindent indents C source files
79+ pgjindent indents Java source files
7980 pginclude scripts for adding/removing include files
8081 unused_oids in pgsql/src/include/catalog
8182</ PRE >
@@ -112,7 +113,7 @@ <H3><A name="1">1</A>) What tools are available for
112113 Others prefer< I > glimpse.</ I >
113114
114115< P > < I > make_diff</ I > has tools to create patch diff files that can
115- be applied to the distribution.
116+ be applied to the distribution. This produces context diffs, which
116117 is our preferred format.</ P >
117118
118119< P > Our standard format is to indent each code level with one tab,
@@ -163,10 +164,14 @@ <H3><A name="1">1</A>) What tools are available for
163164 consistent. Comment blocks that need specific line breaks should be
164165 formatted as< I > block comments,</ I > where the comment starts as
165166< CODE > /*------</ CODE > . These comments will not be reformatted in
166- any way.< I > pginclude</ I > contains scripts used to add needed
167- #include's to include files, and removed unneeded #include's. When
168- adding system types, you will need to assign oids to them. There is
169- also a script called< I > unused_oids</ I > in
167+ any way.</ P >
168+
169+ < P > < I > pginclude</ I > contains scripts used to add needed
170+ < CODE > #include</ CODE > 's to include files, and removed unneeded
171+ < CODE > #include</ CODE > 's.</ P >
172+
173+ < P > When adding system types, you will need to assign oids to them.
174+ There is also a script called< I > unused_oids</ I > in
170175< I > pgsql/src/include/catalog</ I > that shows the unused oids.</ P >
171176
172177< H3 > < A name ="2 "> 2</ A > ) What books are good for developers?</ H3 >