X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fgnulib-intro.texi;h=d962ace7a23b24a89efd094186f4be88eede1e41;hb=75ca5935f84fedf0eb6611245cc28555036d2090;hp=e2d388d6b06bf1c93fd0a19bb57b1ae14cf82cb2;hpb=a0c6d64df03b9dbbe9515d47f72f5639174abc80;p=gnulib.git

diff --git a/doc/gnulib-intro.texi b/doc/gnulib-intro.texi
index e2d388d6b..d962ace7a 100644
--- a/doc/gnulib-intro.texi
+++ b/doc/gnulib-intro.texi
@@ -89,14 +89,12 @@ Some operating systems are not very widespread, but are Free Software and
 are actively developed.  Such platforms are also supported by Gnulib, if
 that OS's developers community keeps in touch with the Gnulib developers,
 by providing bug reports, analyses, or patches.  For such platforms, Gnulib
-will not support all versions that are at most three years old, but only
-the versions of the last year or the last few months, depending on the
-maturity of said OS project, the number of its users, and how often these
-users upgrade.
+supports only the versions of the last year or the last few months,
+depending on the maturity of said OS project, the number of its users, and
+how often these users upgrade.
 
 Niche operating systems are generally unsupported by Gnulib, unless some
-people from their developers or users community contributes support to
-Gnulib.
+of their developers or users contribute support to Gnulib.
 
 The degree of support Gnulib guarantees for a platform depends on the
 amount of testing it gets from volunteers.  Platforms on which Gnulib
@@ -110,7 +108,7 @@ As of 2011, the list of supported platforms is the following:
 
 @itemize
 @item
-glibc systems.  With glibc 2.8 or newer, they are frequenty tested.  With
+glibc systems.  With glibc 2.8 or newer, they are frequently tested.  With
 glibc 2.3 or newer, they are occasionally tested.
 @item
 MacOS X.  In versions 10.5 and 10.6, it's frequently tested.  In version
@@ -135,7 +133,7 @@ OSF/1 5.1 is occasionally tested.  OSF/1 4.0 is rarely tested and low
 priority.
 @item
 Solaris 8 and newer are occasionally tested.  Solaris 7 is rarely tested.
-Solaris 2.6 and older is rarely tested and low priority.
+Solaris 2.6 and older are rarely tested and low priority.
 @item
 Cygwin 1.7.x is frequently tested.  Cygwin 1.5.x is occasionally tested.
 @item
@@ -146,10 +144,12 @@ unsupported on mingw: @code{mgetgroups}, @code{getugroups}, @code{idcache},
 @code{mkancesdirs}, @code{mkdir-p}, @code{euidaccess}, @code{faccessat}.
 The versions of Windows that are supported are Windows XP and newer.
 @item
-Native Windows, with MSVC as compiler, is not tested and low priority.
+Native Windows, with MSVC as compiler, is rarely tested and low priority.
 @item
 mingw in 64-bit mode is not tested and low priority so far.
 @item
+Interix 6.1 is rarely tested, and requires the @code{suacomp} library
+(@url{http://sourceforge.net/projects/suacomp/}) in version 0.6.8 or newer.
 Interix 3.5 is not tested.
 @item
 Haiku is rarely tested, BeOS is not tested and low priority.
@@ -159,7 +159,7 @@ uClibc on Linux is rarely tested.
 QNX is not tested and low priority.
 @end itemize
 
-These operating systems are all supported in an unvirtualized environment.
+Gnulib supports these operating systems only in an unvirtualized environment.
 When you run an OS inside a virtual machine, you have to be aware that the
 virtual machine can bring in bugs of its own.  For example, floating-point
 operations on Solaris can behave slightly differently in QEMU than on real
@@ -170,8 +170,11 @@ Similarly, running native Windows binaries on GNU/Linux under WINE is
 rarely tested and low priority: WINE has a set of behaviours and bugs that
 is slightly different from native Windows.
 
-The following platforms are @emph{not} supported by Gnulib.  Even correct
-patches for their support will not be applied.
+The following platforms are not supported by Gnulib.  The cost of
+supporting them would exceed the benefit because they are rarely used, or
+poorly documented, or have been supplanted by other platforms, or diverge
+too much from POSIX, or some combination of these and other factors.
+Please don't bother sending us patches for them.
 
 @itemize
 @item
@@ -301,8 +304,8 @@ against the out-of-memory condition.
 Examples are a module for copying a file --- the portability problems
 relate to the copying of the file's modification time, access rights,
 and extended attributes --- or a module for extracting the tail
-component of a file name --- here the portability to Woe32 requires a
-different API than the classical POSIX @code{basename} function.
+component of a file name --- here the portability to native Windows
+requires a different API than the classical POSIX @code{basename} function.
 
 @subsection Reusable application code