From 5286ccbaf9a0c59582ff5486a7703394e57329cb Mon Sep 17 00:00:00 2001 From: Chris Allegretta Date: Wed, 9 Aug 2000 22:09:38 +0000 Subject: [PATCH] 0.9.16 release git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@181 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- configure | 2 +- configure.in | 2 +- faq.html | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/configure b/configure index f6a9539a..367ce249 100755 --- 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 index 5bfdc8d1..65dcb713 100644 --- 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 index e3696850..4d67ad76 100644 --- a/faq.html +++ b/faq.html @@ -183,7 +183,7 @@ nano was developed). of nano?
The current version of nano *should* -be 0.9.15.  Of course you should always check the nano hompage to +be 0.9.16.  Of course you should always check the nano hompage to see what the latest and greatest version is.