summaryrefslogtreecommitdiff
path: root/contrib
diff options
context:
space:
mode:
authorStefano Lattarini <stefano.lattarini@gmail.com>2012-02-06 22:45:47 +0100
committerStefano Lattarini <stefano.lattarini@gmail.com>2012-02-06 22:45:47 +0100
commit21f979352aa120457b09e4487f5e23a72d8c3dce (patch)
tree40e5c6ae2b21165cf177fdb77d6d0fa97d30ebad /contrib
parentd7dca5af7aa33024228e7bc21a86383ded4ab2bc (diff)
downloadautomake-21f979352aa120457b09e4487f5e23a72d8c3dce.tar.gz
cosmetics: few whitespace fixlets
Diffstat (limited to 'contrib')
-rw-r--r--contrib/README3
1 files changed, 1 insertions, 2 deletions
diff --git a/contrib/README b/contrib/README
index bbef72fbc..a4d7eeb8d 100644
--- a/contrib/README
+++ b/contrib/README
@@ -14,7 +14,7 @@ There are several reasons for which a feature can be kept in contrib:
core (as doing so too early would later force us to continue the
support for backward-compatibility, even if the features proves
flawed or fails to attract widespread use).
-
+
2. The APIs or overall design of the feature are still unstable, and
need on-field testing to iron warts and usability bugs, or uncover
potential flaws.
@@ -24,4 +24,3 @@ There are several reasons for which a feature can be kept in contrib:
remove it from the Automake core, but cannot remove it altogether,
for the sake of those still-existing usage. So it gets moved in
contrib.
-