From: Steven Rostedt <rostedt@goodmis.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtracefs: unbreak parallel build
Date: Mon, 11 Jul 2022 12:43:26 -0400 [thread overview]
Message-ID: <20220711124326.75f06c4d@gandalf.local.home> (raw)
In-Reply-To: <20220624210726.84857-1-jengelh@inai.de>
On Fri, 24 Jun 2022 23:07:26 +0200
Jan Engelhardt <jengelh@inai.de> wrote:
> Entering a directory concurrently is worse than anything the
> "recursive make considered harmful" essay could ever think of.
>
> Signed-off-by: Jan Engelhardt <jengelh@inai.de>
Applied, thanks Jan!
-- Steve
prev parent reply other threads:[~2022-07-11 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 21:07 [PATCH] libtracefs: unbreak parallel build Jan Engelhardt
2022-07-11 16:43 ` Steven Rostedt [this message]
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=20220711124326.75f06c4d@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).