nano

commit 5286ccbaf9a0c59582ff5486a7703394e57329cb
parent ba96f7afac79bba691c78bec0551ea9d95f87ed8
Author: Chris Allegretta <chrisa@asty.org>
Date:   Wed,  9 Aug 2000 22:09:38 +0000

0.9.16 release


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@181 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

Diffstat:
M
configure
 | 
2
+-
M
configure.in
 | 
2
+-
M
faq.html
 | 
2
+-

3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/configure b/configure
@@ -710,7 +710,7 @@ fi
 
 PACKAGE=nano
 
-VERSION=0.9.15-cvs
+VERSION=0.9.16
 
 if test "`cd $srcdir && pwd`" != "`pwd`" && test -f $srcdir/config.status; then
   { echo "configure: error: source directory already configured; run "make distclean" there first" 1>&2; exit 1; }
diff --git a/configure.in b/configure.in
@@ -1,7 +1,7 @@
 # $Id$
 dnl Process this file with autoconf to produce a configure script.
 AC_INIT(nano.c)
-AM_INIT_AUTOMAKE(nano, 0.9.15-cvs)
+AM_INIT_AUTOMAKE(nano, 0.9.16)
 AM_CONFIG_HEADER(config.h:config.h.in)
 ALL_LINGUAS="es de fr it id fi"
 
diff --git a/faq.html b/faq.html
@@ -183,7 +183,7 @@ nano was developed).</font></blockquote>
 of nano?</font></h2>
 
 <blockquote><font color="#330000">The current version of nano *should*
-be 0.9.15.&nbsp; Of course you should always check the nano hompage to
+be 0.9.16.&nbsp; Of course you should always check the nano hompage to
 see what the latest and greatest version is.</font></blockquote>
 
 <h2>