Re: [PATCH] maint: mention how to run a single test in HACKING docs

[Jim Meyering]

Pádraig Brady <address@hidden> wrote:

> Ralf Wildenhues wrote:
>>> Pádraig Brady <P <at> draigBrady.com> wrote:
>>>> +  env DEBUG=yes VERBOSE=yes make check -C tests TESTS=mv/hard-link-1 >> 
>>>> log
>> 2>&1
>>
>> FWIW, 'make -C' is GNU make-specific, the portable equivalent would be
>>   cd tests && env DEBUG=yes VERBOSE=yes make check TESTS=...
>
> Good point. The attached patch says:
>
> (cd tests && make check TESTS=misc/newtest VERBOSE=yes)
>
>> and catering to even more ugly make issues (macro settings on the command 
>> line
>> not being passed down to sub-make invocations; and automake causing check to
>> invoke a sub-make for the check-TESTS target), it would be:
>>   cd tests && env DEBUG=yes VERBOSE=yes TESTS=... make -e check
>>
>> Of course, -e has its own set of problems, depending on what the user has
>> set in the environment already.
>
> I'm not worrying about the above for the moment.
>
> thanks,
> Pádraig.
>>From 48cae1e8642684f0103848b84d5884d1ba2412c8 Mon Sep 17 00:00:00 2001
> From: =?utf-8?q?P=C3=A1draig=20Brady?= <address@hidden>
> Date: Thu, 12 Feb 2009 13:51:03 +0000
> Subject: [PATCH] maint: mention how to run a single test in HACKING docs
>
> * HACKING: Give an example of how to run a test in isolation.
> * README: Fix/simplify example for running a single test.
> * README-hacking: Reference the HACKING file.

Fine by me.