[GRASSweb-list]markus: web/devel devel.inc,1.22,1.23

[grass at intevation.de]

Author: markus

Update of /grassrepository/web/devel
In directory doto:/tmp/cvs-serv30261

Modified Files:
	devel.inc 
Log Message:
updated

Index: devel.inc
===================================================================
RCS file: /grassrepository/web/devel/devel.inc,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- devel.inc	15 Jan 2006 20:44:29 -0000	1.22
+++ devel.inc	17 Jan 2006 21:08:40 -0000	1.23
@@ -27,15 +27,14 @@
 develop their own unique tools and applications for GRASS. If you develop
 tools and techniques that you feel would benefit other GRASS users, let us
 know! We strongly recommend to follow the coding style described in
-SUBMITTING file (which you find in the main directory of GRASS source code).
+SUBMITTING file (which you find in the main directory of GRASS source code
+or also below).
 
 GRASS GIS is developed and supported by a worldwide <a
-href=http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass/AUTHORS>developers
-team</a> [see the incomplete <a
-href=http://pweb.jps.net/~egm2/grassppl.html>GRASS Developers World Map</a>
-(big: 500k)]. As GRASS is growing, we have plenty of opportunities to join
+href="http://freegis.org/cgi-bin/viewcvs.cgi/~checkout~/grass6/AUTHORS">developers
+team</a>. As GRASS is growing, we have plenty of opportunities to join
 the GRASS development team and improve the powerful GRASS GIS under terms of
-<a href=http://www.gnu.org/copyleft/gpl.html>GNU General Public License</a>.
+<a href="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</a>.
 
 <p>
 <a href="grasscredits.html">Many people</a> have contributed to the GRASS
@@ -95,9 +94,9 @@
 also offer <a href="../download/index.php">precompiled binaries</a>).
 <br>
 The <b>configuration</b> requires a set of installed libraries which are
-described in the file <a href="../grass60/source/REQUIREMENTS.html">REQUIREMENTS.html</a>
+described in the file <a href="../grass61/source/REQUIREMENTS.html">REQUIREMENTS.html</a>
 file (which you also find in the main directory of the source code tarball).
-The <b>compilation</b> is desribed in the <a href="../grass60/source/INSTALL">INSTALL</a>
+The <b>compilation</b> is desribed in the <a href="../grass61/source/INSTALL">INSTALL</a>
 file (which you also find in the main directory of the source code tarball).
 Dear Newbie, please be so kind to search the 
 <a href="../searchgrass.php">developers mailing list archive</a> before asking
@@ -151,11 +150,11 @@
 <ul>
 <li> C language Coding standards: Check your code against the rules defined in the
      'SUBMITTING' file (find it in the main directory of the GRASS source
-     code and also <a href=../grass61/source/SUBMITTING>here</a>). This ensures
+     code and also <a href=../grass61/source/SUBMITTING>SUBMITTING</a>). This ensures
      a smooth integration into the standard GRASS code base.
 <li> Shell script Coding standards: Check your code against the rules defined in the
      'SUBMITTING_SCRIPTS' file (find it in the main directory of the GRASS source
-     code and also <a href=../grass61/source/SUBMITTING_SCRIPTS>here</a>). This ensures
+     code and also <a href=../grass61/source/SUBMITTING_SCRIPTS>SUBMITTING_SCRIPTS</a>). This ensures
      a smooth integration into the standard GRASS code base and avoids portability
      problems.
 <li> Code submission: Please contact a member of the