At Monday 12 April 2010, Ralf Wildenhues ralf.wildenh...@gmx.de
wrote:
The analysis is required in any case. That doesn't mean it is
necessary to mention it in the log message; because even if the
analysis is hard work, in this case it is straight-forward. IOW,
the size of the log
* Stefano Lattarini wrote on Fri, Apr 09, 2010 at 02:19:32AM CEST:
Avoid possible false negatives in cond46.test.
* tests/cond46.test: Enable shell `errexit' flag (and bumped
copyright years). Due to this change, the testcase should now
fail on unexpected failures in calls to
At Sunday 11 April 2010, Ralf Wildenhues ralf.wildenh...@gmx.de
wrote:
* Stefano Lattarini wrote on Fri, Apr 09, 2010 at 02:19:32AM CEST:
Avoid possible false negatives in cond46.test.
* tests/cond46.test: Enable shell `errexit' flag (and bumped
copyright years). Due to this change, the
At Sunday 11 April 2010, Ralf Wildenhues ralf.wildenh...@gmx.de
wrote:
How'd you suggest to shorten the log entry above, while keeping
it meaningful?
By cutting the part which I did not quote. :-)
Oops, I missed that.
Being verbose is fine for things that are unobvious, but you may
* Stefano Lattarini wrote on Sun, Apr 11, 2010 at 10:30:19PM CEST:
At Sunday 11 April 2010, Ralf Wildenhues wrote:
Being verbose is fine for things that are unobvious, but you may
assume that developers know autoconf.info.
Quite right. However, as you said when discussing my proposed patch
), and returns
with a status of `0' otherwise (thus avoiding the possibility of
false positives).
From e7daa4e00f92b0a091710070832dd0e10a06e739 Mon Sep 17 00:00:00 2001
From: Stefano Lattarini stefano.lattar...@gmail.com
Date: Fri, 9 Apr 2010 01:27:23 +0200
Subject: [PATCH] Avoid possible false
