From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: John Kacur <jkacur@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Wagner <dwagner@suse.de>
Subject: Re: [PATCH v2] rtla: Remove procps-ng dependency
Date: Thu, 5 May 2022 18:21:28 +0200 [thread overview]
Message-ID: <e5fec585-932f-db71-f435-3f837a177dbc@kernel.org> (raw)
In-Reply-To: <cd9251-c95-b342-3694-777945cc374@redhat.com>
On 5/5/22 18:16, John Kacur wrote:
> If we were to add a package that depended on it, it would then be
> available at runtime. I would remove any references to RHEL in your
> description, and just say you are reducing the dependency on this to
> simply building rtla.
If I try to install today, it is not there. I am not saying it would not be
there. It is an argument that it it not that used, and it is correct.
-- Daniel
next prev parent reply other threads:[~2022-05-05 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 13:01 Daniel Bristot de Oliveira
2022-05-05 16:16 ` John Kacur
2022-05-05 16:21 ` Daniel Bristot de Oliveira [this message]
2022-05-06 15:06 ` Tao Zhou
2022-05-06 15:39 ` Daniel Bristot de Oliveira
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=e5fec585-932f-db71-f435-3f837a177dbc@kernel.org \
--to=bristot@kernel.org \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®