From: "Frank Ch. Eigler" <fche@elastic.org>
To: Serhei Makarov <serhei@serhei.io>
Cc: Mark Wielaard <mark@klomp.org>,
buildbot@sourceware.org, systemtap <systemtap@sourceware.org>
Subject: Re: [PATCH] rhel10-x86_64: add systemtap builder
Date: Mon, 24 Feb 2025 13:48:21 -0500 [thread overview]
Message-ID: <Z7y-9eLTTU2TtfqO@elastic.org> (raw)
In-Reply-To: <f84263a9-f1d7-426f-8958-a21f50129a77@app.fastmail.com>
Hi -
> > It would also be good to explain on list what this "rhel10" exactly
> > is. I don't believe others can easily replicate it (or is it really
> > c10s?)
RHEL10-beta has been made available to RHEL customers months ago, AIUI
including freebie RHEL developer subscription users. It's not mystery
meat.
> Would it be worth renaming either 'stap' or 'systemtap' in a way
> that makes the distinction more obvious?
(I don't think it really matters. tag=systemtap finds them both, no
big deal.)
- FChE
prev parent reply other threads:[~2025-02-24 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 17:44 Serhei Makarov
2025-02-20 20:20 ` Mark Wielaard
[not found] ` <20250220203025.GI11999@gnu.wildebeest.org>
2025-02-24 18:42 ` Serhei Makarov
2025-02-24 18:48 ` Frank Ch. Eigler [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=Z7y-9eLTTU2TtfqO@elastic.org \
--to=fche@elastic.org \
--cc=buildbot@sourceware.org \
--cc=mark@klomp.org \
--cc=serhei@serhei.io \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).