From: "Michael Kjörling" <email@example.com>
Subject: [COFF] Re: Alpine
Date: Wed, 13 Jul 2022 07:36:37 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 13 Jul 2022 09:34 +1000, from email@example.com (Dave Horsfall):
>> If Wikipedia is to be believed, the MUA came later.
>> <https://en.wikipedia.org/wiki/Alpine_Linux> "Initial release August 2005"
>> as compared to
>> <https://en.wikipedia.org/wiki/Alpine_(email_client)> "Initial release December 20, 2007"
> Any fool can update Wikipedia (and they do).
> I give you PINE (Alpine's (predecessor):
> 1992... I've been using it (then Alpine) since about then.
Sure; I used Pine in 1995-1996 or so, and then again around 2001-2002,
so yes, Pine clearly predates a Linux distribution with an initial
release in mid-2005. But your post was about _Alpine_, not _Pine_ (or
at least, I can't immediately find any "Pine Linux", whereas Alpine
Linux is rather well-known), so that's what I was responding to.
Michael Kjörling • https://michael.kjorling.se • firstname.lastname@example.org
“Remember when, on the Internet, nobody cared that you were a dog?”
next prev parent reply other threads:[~2022-07-13 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 7:40 [COFF] Systemd Creator Lands At Microsoft Tomasz Rola
2022-07-08 10:26 ` [COFF] " Michael Cardell Widerkrantz
2022-07-09 0:29 ` Tomasz Rola
2022-07-09 1:52 ` Angel M Alganza
2022-07-09 8:35 ` Tomasz Rola
2022-07-09 8:59 ` Angel M Alganza
2022-07-10 21:39 ` Chris Hanson
2022-07-11 14:11 ` Steffen Nurpmeso
2022-07-11 21:04 ` Michael Cardell Widerkrantz
2022-07-11 23:01 ` Dave Horsfall
2022-07-12 7:58 ` [COFF] Re: Alpine, was: " Michael Kjörling
2022-07-12 15:34 ` Adam Thornton
2022-07-12 22:02 ` Steffen Nurpmeso
2022-07-12 23:34 ` Dave Horsfall
2022-07-13 7:36 ` Michael Kjörling [this message]
2022-07-12 15:56 ` [COFF] " Michael Cardell Widerkrantz
2022-07-12 19:48 ` Lars Brinkhoff
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).