From: Steven Rostedt <rostedt@goodmis.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtracefs: avoid pointless extra DEP stage
Date: Fri, 8 Jul 2022 14:22:48 -0400 [thread overview]
Message-ID: <20220708142248.19af0aa9@gandalf.local.home> (raw)
In-Reply-To: <20220620150316.21022-1-jengelh@inai.de>
On Mon, 20 Jun 2022 17:03:16 +0200
Jan Engelhardt <jengelh@inai.de> wrote:
> clean:
> - $(Q)$(call do_clean,$(OBJS) .*.d)
> + $(Q)$(call do_clean,$(OBJS) *.d)
>
> -dep_includes := $(wildcard $(DEPS))
> -
> -ifneq ($(dep_includes),)
> - include $(dep_includes)
> -endif
> +-include *.d
>
After this change, the .d files are visible. Is there a way to keep them
hidden? That is, keep the . in front?
-- Steve
next prev parent reply other threads:[~2022-07-08 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 15:03 [PATCH] libtracefs: avoid pointless extra DEP stage Jan Engelhardt
2022-07-08 18:22 ` Steven Rostedt [this message]
2022-07-11 19:37 ` Jan Engelhardt
2022-07-11 20:52 ` [PATCH v2] " Jan Engelhardt
2022-07-14 14:46 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220708142248.19af0aa9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jengelh@inai.de \
--cc=linux-trace-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).