From: adam@westernsemico•com
To: depot@tvl.su
Cc: Vincent Ambo <mail@tazj•in>
Subject: {test of, comment on} the TVL mailing list
Date: Mon, 02 Jan 2023 22:47:02 -0800 [thread overview]
Message-ID: <167272842233.26690.8814024501802381795@localhost> (raw)
In-Reply-To: <CANHrikpW26QWm6Bw8LuK1EpcC2kVVWnuwfqE+0B9jW7P5iAzPA@mail.gmail.com>
Hello, this is a test.
Quoting Vincent Ambo (2022-12-26 00:01:13)
> mailing list at depot@tazj.in to a public-inbox setup
Excellent taste in software, as I have come to expect from TVL ;)
> It is essentially like a pull-based mailing list
Yet another ahead-of-its-time [DJB idea] comes to fruition...
- a
[DJB idea]: https://en.wikipedia.org/wiki/Internet_Mail_2000
next parent reply other threads:[~2023-01-03 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANHrikpW26QWm6Bw8LuK1EpcC2kVVWnuwfqE+0B9jW7P5iAzPA@mail.gmail.com>
2023-01-03 6:47 ` adam [this message]
2023-01-03 12:56 ` Vincent Ambo
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=167272842233.26690.8814024501802381795@localhost \
--to=adam@westernsemico$(echo .)com \
--cc=depot@tvl.su \
--cc=mail@tazj$(echo .)in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://code.tvl.fyi
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).