summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2010-03-01 23:12:37 -0700
committerEric Blake <eblake@redhat.com>2010-03-01 23:12:37 -0700
commitc2c3cad235534230e9287770c0db4652d3b4833a (patch)
tree0b8e5250bbe3bb13427459b13d713801118e313e /README
parent747b093a76d4934534994ddb8c0ddbb33b593f8c (diff)
downloadm4-c2c3cad235534230e9287770c0db4652d3b4833a.tar.gz
Mention release of version 1.4.14.
* gnulib: Update to latest. * README: Drop CVS mention. * HACKING: Tweak release instructions. * NEWS: Mention the release. * .prev-version: Record previous version. * cfg.mk (old_NEWS_hash): Auto-update. Signed-off-by: Eric Blake <eblake@redhat.com> (cherry picked from commit a90f35d7c17b51e8afea9f6d7e2daddeff135c9d)
Diffstat (limited to 'README')
-rw-r--r--README4
1 files changed, 2 insertions, 2 deletions
diff --git a/README b/README
index c1cfe2e8..3caf6c6e 100644
--- a/README
+++ b/README
@@ -17,8 +17,8 @@ process requires that you first install a released copy of GNU `m4'.
If you are just trying to build `m4' from a released tarball, you
should not normally need to run `./bootstrap' or `autoreconf'; just go
ahead and start with `./configure'. If you are trying to build `m4'
-from git or CVS, more information can be found in the file HACKING,
-only found in a version control checkout.
+from git, more information can be found in the version-control-only
+file HACKING.
In the subdirectories `tests' and `examples' you will find various m4
files, ranging from trivial test files to rather advanced macros. If