diff --git a/README-dev b/README-dev
line changes: +39/-0
index 0000000..0647e78
--- /dev/null
+++ b/README-dev

@@ -0,0 +1,39 @@
+This README.dev file describes the development environment.
+
+  Copyright (C) 2002, 2003, 2005, 2006, 2008 Free Software Foundation, Inc.
+
+  Copying and distribution of this file, with or without modification,
+  are permitted in any medium without royalty provided the copyright
+  notice and this notice are preserved.
+
+The development sources are available through anonymous CVS at Savannah:
+  http://savannah.gnu.org/cvs/?group=hello
+
+This distribution uses whatever versions of Automake, Autoconf, and
+Gettext are listed in NEWS; usually the latest ones released.  If you
+are getting the sources from CVS (or change configure.ac), you'll need
+to have these tools installed to (re)build.  You'll also need help2man.
+All of these programs are available from ftp://ftp.gnu.org/gnu.
+
+This distribution also uses Gnulib (http://www.gnu.org/software/gnulib)
+to share common files, with the files being checked in to CVS.  If you
+want to update from the current gnulib, do a cvs checkout of gnulib, and
+then run
+  gnulib-tool --import
+in the top-level directory.
+
+For the record, the first time invocation was
+  gnulib-tool --import --m4-base=gnulib/m4 --source-base=gnulib/lib \
+              --no-vc-files getopt
+Many more modules have been added since.  The currently-used gnulib
+modules and other gnulib information are recorded in
+gnulib/m4/gnulib-cache.m4.  Given a source checkout of gnulib, you can
+update the files with gnulib-tool --import.
+
+When updating gettext, besides the normal installation on the system, it
+is necessary to run gettextize -f in this hierarchy to update the po/
+infrastructure.  This is in addition to the gettext gnulib module.
+
+After getting the CVS sources, and installing the tools above, you can run
+  sh ./autogen.sh
+to do a fresh build.  After that first time, running make should suffice.

diff --git a/README.dev b/README.dev
line changes: +0/-39
index 0647e78..0000000
--- a/README.dev
+++ /dev/null

@@ -1,39 +0,0 @@
-This README.dev file describes the development environment.
-
-  Copyright (C) 2002, 2003, 2005, 2006, 2008 Free Software Foundation, Inc.
-
-  Copying and distribution of this file, with or without modification,
-  are permitted in any medium without royalty provided the copyright
-  notice and this notice are preserved.
-
-The development sources are available through anonymous CVS at Savannah:
-  http://savannah.gnu.org/cvs/?group=hello
-
-This distribution uses whatever versions of Automake, Autoconf, and
-Gettext are listed in NEWS; usually the latest ones released.  If you
-are getting the sources from CVS (or change configure.ac), you'll need
-to have these tools installed to (re)build.  You'll also need help2man.
-All of these programs are available from ftp://ftp.gnu.org/gnu.
-
-This distribution also uses Gnulib (http://www.gnu.org/software/gnulib)
-to share common files, with the files being checked in to CVS.  If you
-want to update from the current gnulib, do a cvs checkout of gnulib, and
-then run
-  gnulib-tool --import
-in the top-level directory.
-
-For the record, the first time invocation was
-  gnulib-tool --import --m4-base=gnulib/m4 --source-base=gnulib/lib \
-              --no-vc-files getopt
-Many more modules have been added since.  The currently-used gnulib
-modules and other gnulib information are recorded in
-gnulib/m4/gnulib-cache.m4.  Given a source checkout of gnulib, you can
-update the files with gnulib-tool --import.
-
-When updating gettext, besides the normal installation on the system, it
-is necessary to run gettextize -f in this hierarchy to update the po/
-infrastructure.  This is in addition to the gettext gnulib module.
-
-After getting the CVS sources, and installing the tools above, you can run
-  sh ./autogen.sh
-to do a fresh build.  After that first time, running make should suffice.