On 2/20/25 17:23, Karl Berry wrote:
It's not practical to ship a C file and
compile that when the user runs the tests (right?).
Right. Also right that we don't want to induce a dependency on
perl/python/whatever for running tests.
(a) not piping stderr through the prefixing funct
On 2/20/25 17:23, Karl Berry wrote:
Hi Richard and Jacob,
rh> can switch to a separate email per commit if preferred.
No need. For most purposes, it's much more convenient to have one email
with the whole patch series than many individual messages. I'll save the
patches to separate files.
* m4/sanity.m4 (AM_SANITY_CHECK): Call AC_MSG_RESULT before erroring
out so that a complete line is printed to stdout before the error
message is written to stderr.
---
m4/sanity.m4 | 2 ++
1 file changed, 2 insertions(+)
diff --git a/m4/sanity.m4 b/m4/sanity.m4
index 53538a873..be4b16113 100644
* m4/sanity.m4 (AM_SANITY_CHECK): Call AC_MSG_RESULT before erroring
out so that a complete line is printed to stdout before the error
message is written to stderr.
I pushed this. (surprisingly, no tests failed for me. :)
Thanks Richard.
Hi Richard and Jacob,
rh> can switch to a separate email per commit if preferred.
No need. For most purposes, it's much more convenient to have one email
with the whole patch series than many individual messages. I'll save the
patches to separate files.
jb> I suspect that you are having
It's not practical to ship a C file and
compile that when the user runs the tests (right?).
Right. Also right that we don't want to induce a dependency on
perl/python/whatever for running tests.
(a) not piping stderr through the prefixing function when the prefix
is the empty str
