From: Dennis Clarke <dclarke@blastwave.org>
To: tomas@tuxteam.de, libc-help@sourceware.org
Subject: Re: Richard M. Stallman says GNU/Linux, but Rust lang ecosystem is growing.
Date: Mon, 1 Apr 2024 21:44:56 -0400 [thread overview]
Message-ID: <7d20209d-188c-4441-9dd1-9110e7e6380f@blastwave.org> (raw)
In-Reply-To: <Zgl4OsZHCfyugp/m@tuxteam.de>
On 3/31/24 10:50, tomas@tuxteam.de wrote:
>>> [strange drivel elided]
>>
>> Was it generated using a LLM?
>
> My impression too. Those startups are desperate for feedback and
> training data, so why shouldn't they strip-mine public mailing
> lists for that?
>
> This is why I tend to not answer to such stuff.
Pardon me for being very very old school but Do Not Feed The Trolls.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
next prev parent reply other threads:[~2024-04-02 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 12:43 bingmatv
2024-03-31 14:04 ` Adhemerval Zanella
2024-03-31 14:50 ` tomas
2024-04-02 1:44 ` Dennis Clarke [this message]
2024-04-07 7:27 ` 馬 冰
2024-04-07 7:45 ` Konstantin Kharlamov
2024-04-11 12:05 ` 馬 冰
2024-04-11 12:12 ` Konstantin Kharlamov
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=7d20209d-188c-4441-9dd1-9110e7e6380f@blastwave.org \
--to=dclarke@blastwave.org \
--cc=libc-help@sourceware.org \
--cc=tomas@tuxteam.de \
/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).