Pádraig Brady <[email protected]> wrote:
...
> diff --git a/HACKING b/HACKING
> index 6eb0480..c8e85f8 100644
> --- a/HACKING
> +++ b/HACKING
> @@ -288,7 +288,9 @@ Nearly every significant change must be accompanied by a
> test suite
> addition that exercises it. If you fix a bug, add at least one test that
> fails without the patch, but that succeeds once your patch is applied.
> If you add a feature, add tests to exercise as much of the new code
> -as possible.
> +as possible. Note to run tests/misc/newtest in isolation you can do:
> +
> + make check -C tests TESTS=newtest VERBOSE=yes
The name after TESTS= should be the name of the file relative to
the tests/ directory:
make check -C tests TESTS=misc/newtest VERBOSE=yes
Thanks!
_______________________________________________
Bug-coreutils mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-coreutils
