more link back to legacy_faq in release notes and what's changed

git-svn-id: http://svn.osgeo.org/postgis/trunk@7062 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/release_notes.xml b/doc/release_notes.xml
index 290b8bce80a9556419945c701741a24ab197a603..6cf3ce3636c3db13bc060e7c693f90b8c217d94e 100644 (file)
--- a/doc/release_notes.xml
+++ b/doc/release_notes.xml
@@ -14,7 +14,8 @@
                <para>-- If you have been using deprecated functions CHANGE your apps or suffer the consequences.
      If you don't see a function documented -- it ain't supported or it is an internal function.
      Some constraints in older tables were built with deprecated functions.
-     If you restore you may need to rebuild table constraints with populate_geometry_columns().</para>
+     If you restore you may need to rebuild table constraints with populate_geometry_columns().  If you have applications or tools
+                                       that rely on deprecated functions, please refer to <link linked="legacy_faq" /> for more details.</para>
         <para>#817 Renaming old 3D functions to the convention ST_3D (Nicklas Avén)</para>
         <para>#548 (sorta), ST_NumGeometries,ST_GeometryN now returns 1 (or the geometry) instead of null 
      for single geometries (Sandro Santilli, Maxime van Noppen)</para>

diff --git a/doc/xsl/postgis_aggs_mm.xml.xsl b/doc/xsl/postgis_aggs_mm.xml.xsl
index a30aa94689d675d826f5ac93458adc6efe083104..ccad3016ae9eac84077ec613b15e2988cdfc2ffd 100644 (file)
--- a/doc/xsl/postgis_aggs_mm.xml.xsl
+++ b/doc/xsl/postgis_aggs_mm.xml.xsl
@@ -502,7 +502,8 @@
                                <para>The functions given below are PostGIS functions that have changed behavior in PostGIS 2.0.</para>
                                <note><para>Most deprecated functions have been removed.  These are functions that haven't been documented since 1.2
                                        or some internal functions that were never documented.  If you are using a function that you don't see documented,
-                                       it's probably deprecated, about to be deprecated, or internal and should be avoided.</para></note>
+                                       it's probably deprecated, about to be deprecated, or internal and should be avoided.  If you have applications or tools
+                                       that rely on deprecated functions, please refer to <link linked="legacy_faq" /> for more details.</para></note>
                                <itemizedlist>
                                <!-- Pull out the purpose section for each ref entry   -->
                                        <xsl:for-each select='//refentry'>