From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@infradead.org>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] LTTng upstreaming next steps
Date: Mon, 14 Jul 2025 16:37:55 -0400 [thread overview]
Message-ID: <20250714163755.1de132e9@gandalf.local.home> (raw)
In-Reply-To: <20250714162750.45b12314@gandalf.local.home>
On Mon, 14 Jul 2025 16:27:50 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> > And very clearly - based on history - that unification will never happen.
>
> Unfortunately, I think you're right. :-(
Actually, let me take that back. I think you are right as long as one is
out of tree. Because there's no incentive to merge them.
If LTTng were to be in tree, it would be much easier to work on a strategy
to merge the infrastructure as the maintainers of both would have better
access to each other's code.
The Linux kernel has had a long history of two or more ways of doing
something that eventually was merged into a single shared infrastructure.
But as long as one is out of tree, it will never happen. That's because it
is much harder to merge infrastructure together when they are separated
like that.
-- Steve
next prev parent reply other threads:[~2025-07-14 20:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 19:41 [RFC] LTTng upstreaming next steps Mathieu Desnoyers
2025-07-14 20:00 ` Linus Torvalds
2025-07-14 20:27 ` Steven Rostedt
2025-07-14 20:37 ` Steven Rostedt [this message]
2025-07-14 21:04 ` Linus Torvalds
2025-07-15 9:24 ` Steven Rostedt
2025-07-15 12:50 ` James Bottomley
2025-07-15 13:16 ` Steven Rostedt
2025-07-15 14:38 ` James Bottomley
2025-07-15 14:50 ` Steven Rostedt
2025-07-15 15:10 ` James Bottomley
2025-07-15 15:16 ` Steven Rostedt
2025-07-15 15:13 ` 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=20250714163755.1de132e9@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).