From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: lartc@vger.kernel.org
Subject: Status of the LARTC project and of this list
Date: Tue, 31 Oct 2023 12:57:49 -0400 [thread overview]
Message-ID: <20231031-apricot-mongrel-of-artistry-c585fd@meerkat> (raw)
Hello, all:
We're in the process of migrating vger lists to new infrastructure and, as
such, we are reviewing all lists that appear inactive to gauge if we need to
consider sunsetting them.
The status of the LARTC project is not very clear to me, which is why I'm
reaching out to list subscribers. From the outset, things aren't looking very
alive:
- the last update to lartc.org is from 2012
- the last update to lartc.git is also from 2012
However, there are still a few questions being asked on the list, which is now
archived here: https://lore.kernel.org/lartc
Does anyone have a good picture of the status of the project? Is it still
relevant?
-K
next reply other threads:[~2023-10-31 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 16:57 Konstantin Ryabitsev [this message]
2023-10-31 20:53 ` Status of the LARTC project and of this list Rich Brown
2023-10-31 22:46 ` Lewis Rosenthal
2023-11-01 0:16 ` Mike Wright
2023-11-01 2:26 ` Grant Taylor
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=20231031-apricot-mongrel-of-artistry-c585fd@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=lartc@vger.kernel.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).