bug-coreutils
[Top][All Lists]
Advanced

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

[PATCH] doc: typo fix in README-hacking


From: Jim Meyering
Subject: [PATCH] doc: typo fix in README-hacking
Date: Sat, 20 Jun 2009 14:49:42 +0200

I've just pushed this:

>From 0975852c5036b54d6d1fa18574d11db5943fba21 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Sat, 20 Jun 2009 14:48:59 +0200
Subject: [PATCH] doc: typo fix in README-hacking

* README-hacking: Fix a typo.
Don't make building from a git-cloned tree sound so hard.
---
 README-hacking |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/README-hacking b/README-hacking
index 152a215..9deba13 100644
--- a/README-hacking
+++ b/README-hacking
@@ -2,7 +2,7 @@

 These notes intend to help people working on the checked-out sources.
 These requirements do not apply when building from a distribution tarball.
-See also HACKING for more detailed coreutils contribution guidlines.
+See also HACKING for more detailed coreutils contribution guidelines.

 * Requirements

@@ -23,8 +23,8 @@ bootstrap script shown below, and will include:
 - Rsync <http://samba.anu.edu.au/rsync/>
 - Tar <http://www.gnu.org/software/tar/>

-Only building the initial full source tree will be a bit painful.
-Later, a plain `git pull && make' should be sufficient.
+While building from a just-cloned source tree may require installing a
+few prerequisites, later, a plain `git pull && make' should be sufficient.

 - Valgrind

--
1.6.3.2.416.g04d0




reply via email to

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