From: Steven Rostedt <rostedt@goodmis.org>
To: "Vladislav Valtchev (VMware)" <vladislav.valtchev@gmail.com>
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
y.karadz@gmail.com
Subject: Re: [PATCH] trace-cmd: Make the build messages to show only file names
Date: Thu, 8 Feb 2018 10:31:15 -0500 [thread overview]
Message-ID: <20180208103115.762f6ee3@gandalf.local.home> (raw)
In-Reply-To: <20180208091820.4920-1-vladislav.valtchev@gmail.com>
On Thu, 8 Feb 2018 11:18:20 +0200
"Vladislav Valtchev (VMware)" <vladislav.valtchev@gmail.com> wrote:
> Currently, the typical trace-cmd build messages like "COMPILE <file>" and
> "BUILD STATIC LIB <file>" show file's full path, instead of just the file
> name, as it used to happen before the full support for out-of-tree builds.
> This simple patch makes the build messages to look exactly like in the past
> by stripping the directory part of each file path, before printing the
> message.
>
>
Thanks, applied!
-- Steve
prev parent reply other threads:[~2018-02-08 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 9:18 Vladislav Valtchev (VMware)
2018-02-08 15:31 ` 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=20180208103115.762f6ee3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=vladislav.valtchev@gmail.com \
--cc=y.karadz@gmail.com \
/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
all inboxes | Powered by JetHome®