[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Patches to README-release
From: |
Jim Meyering |
Subject: |
Re: Patches to README-release |
Date: |
Sat, 28 Jan 2012 10:51:57 +0100 |
Gary V. Vaughan wrote:
> On 28 Jan 2012, at 15:27, Jim Meyering wrote:
>> Gary V. Vaughan wrote:
>>> Hi Jim,
>>>
>>> On 28 ม.ค. 2012, at 1:21, Jim Meyering <address@hidden> wrote:
>>>
>>> Reuben Thomas wrote:
>>>
>>> Ping? The patches still apply cleanly to HEAD.
>>>
>>> On 22 December 2011 19:54, Reuben Thomas <address@hidden> wrote:
>>>
>>> -* Ensure that the desired versions of autoconf, automake, etc.
>>> - are in your PATH. See the buildreq list in bootstrap.conf for
>>> - the complete list.
I see at least one source of confusion.
The use of "desired" above, is not specific enough.
And by "the complete list" I meant "the complete list of tools",
not the list of "tools and desired versions":
I've just pushed this:
>From 0eab6e2c9ef1e852ec8a880e2e134670f3ceb5c2 Mon Sep 17 00:00:00 2001
From: Jim Meyering <address@hidden>
Date: Sat, 28 Jan 2012 10:49:35 +0100
Subject: [PATCH] doc: clarify README-release
* top/README-release: Clarify: you should make a point to have
the latest stable versions of build tools in your PATH, and the
reference to buildreq is solely for its list of tool names, not
for its minimal-functional version numbers.
Prompted by discussion with Reuben Thomas and Gary V. Vaughan.
---
ChangeLog | 7 +++++++
top/README-release | 4 ++--
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index d37f933..e378111 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,12 @@
2012-01-28 Jim Meyering <address@hidden>
+ doc: clarify README-release
+ * top/README-release: Clarify: you should make a point to have
+ the latest stable versions of build tools in your PATH, and the
+ reference to buildreq is solely for its list of tool names, not
+ for its minimal-functional version numbers.
+ Prompted by discussion with Reuben Thomas and Gary V. Vaughan.
+
maint.mk: use more readable (yet functionally equivalent) quoting
It is common to quote a single quote in a single quoted string like
this: '...'\''...'. Unless you know the idiom, that looks like
diff --git a/top/README-release b/top/README-release
index 0020885..d6e032a 100644
--- a/top/README-release
+++ b/top/README-release
@@ -6,9 +6,9 @@ Here are most of the steps we (maintainers) follow when making
a release.
git checkout master
git pull origin master
-* Ensure that the desired versions of autoconf, automake, etc.
+* Ensure that the latest stable versions of autoconf, automake, etc.
are in your PATH. See the buildreq list in bootstrap.conf for
- the complete list.
+ the complete list of tools.
* Ensure that you're on "master" with no uncommitted diffs.
This should produce no output: git checkout master; git diff
--
1.7.9.1.g63eb
- Re: Patches to README-release, Reuben Thomas, 2012/01/27
- Re: Patches to README-release, Jim Meyering, 2012/01/27
- Re: Patches to README-release, Gary V. Vaughan, 2012/01/27
- Re: Patches to README-release, Jim Meyering, 2012/01/28
- Re: Patches to README-release, Gary V. Vaughan, 2012/01/28
- Re: Patches to README-release, Jim Meyering, 2012/01/28
- Re: Patches to README-release, Gary V. Vaughan, 2012/01/28
- Re: Patches to README-release, Jim Meyering, 2012/01/28
- Re: Patches to README-release,
Jim Meyering <=