autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH] README-hacking: fix typo


From: Jim Meyering
Subject: [PATCH] README-hacking: fix typo
Date: Sat, 26 Mar 2011 21:51:15 +0100

Here's a tiny fix:

>From 5941d6d14017f0bcf638b6d61dbb9374f81c3e6f Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Sat, 26 Mar 2011 21:50:43 +0100
Subject: [PATCH] README-hacking: fix typo

* README-hacking: s/just build/just built/.
---
 ChangeLog      |    5 +++++
 README-hacking |    2 +-
 2 files changed, 6 insertions(+), 1 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 30dfced..e741276 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2011-03-26  Jim Meyering  <address@hidden>
+
+       README-hacking: fix typo
+       * README-hacking: s/just build/just built/.
+
 2011-03-08  Colin Watson  <address@hidden>  (tiny change)
            Ralf Wildenhues  <address@hidden>

diff --git a/README-hacking b/README-hacking
index e8d51a0..a15e7d8 100644
--- a/README-hacking
+++ b/README-hacking
@@ -75,7 +75,7 @@ The next step is to generate files like configure and 
Makefile.in:

 Since we're building autoconf itself, and its tests are picky, the
 following procedure includes an extra step to ensure that some
-generated files are regenerated using the tools just build by "make"
+generated files are regenerated using the tools just built by "make"
 (if you use GNU make, the file GNUmakefile sets PATH for you):

   $ ./configure
--
1.7.4.1.688.g95e3e



reply via email to

[Prev in Thread] Current Thread [Next in Thread]