From: Florian Weimer via lttng-dev <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] lttv: Document project status as unmaintained
Date: Wed, 11 Jan 2023 12:01:28 +0100 [thread overview]
Message-ID: <87r0w1cp2v.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <d17dbab6-5222-7065-ae0e-144687b2efc6@efficios.com> (Mathieu Desnoyers's message of "Tue, 10 Jan 2023 14:46:42 -0500")
* Mathieu Desnoyers:
> Hi Florian,
>
> I'll pull your patch into the lttv master branch, but please be aware
> that the LTTV project has not seen activity since 2013, is currently
> unmaintained, and that we do not plan on doing further releases of this
> project. Our efforts were diverted elsewhere on the trace analysis
> front, namely into Trace Compass and Babeltrace.
>
> In order to clarify the situation, I will introduce a commit into
> LTTV's master branch which will remove Yannick Brosseau from the
> maintainer role in the README file, and add this section at the
> beginning:
Understood. Fedora is building a lot of legacy software, and many of
the C99 fixes are in this area.
Thanks,
Florian
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2023-01-11 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 10:54 [lttng-dev] [PATCH] lttv: C99 compatibility fix Florian Weimer via lttng-dev
2023-01-10 19:46 ` [lttng-dev] lttv: Document project status as unmaintained Mathieu Desnoyers via lttng-dev
2023-01-11 11:01 ` Florian Weimer via lttng-dev [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=87r0w1cp2v.fsf@oldenburg.str.redhat.com \
--to=lttng-dev@lists.lttng.org \
--cc=fweimer@redhat.com \
--cc=mathieu.desnoyers@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).