On Sun, Nov 05, 2017 at 05:25:37PM +0100, Luc Van Oostenryck wrote:
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx>
> ---
> Makefile | 12 ++----------
> 1 file changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index afc1efe98..f0f7a5b69 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -233,16 +233,8 @@ check: all
> $(Q)cd validation && ./test-suite
>
>
> -clean: clean-check
> - @rm -f *.[oa] .*.d $(PROGRAMS) version.h
> -clean-check:
> +clean: FORCE
> @echo ' CLEAN'
> - @find validation/ \( -name "*.c.output.expected" \
> - -o -name "*.c.output.got" \
> - -o -name "*.c.output.diff" \
> - -o -name "*.c.error.expected" \
> - -o -name "*.c.error.got" \
> - -o -name "*.c.error.diff" \
> - \) -exec rm {} \;
> + @git clean -q -d -x -e .sparse.mk -e '*.[ch]'
No, you can't use git-clean here, for two reasons.
First, it has to be possible to build, and clean, sparse from a
tarball release, not just a git repository.
And second, even if not for that, this should *not* use -x or -d, *only*
-X. Otherwise, you might remove, say, a pile of carefully written
patches and cover letters sitting in the user's Sparse source directory.
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
