From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: Oh, my
Date: Mon, 01 Feb 2021 02:42:07 -0600 [thread overview]
Message-ID: <53e8ebef-ed82-d69e-5959-55b363499519@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
My goodness, my gracious, me oh my!
The recent flurry of contributions on this list is inspiring!
There was a HUGE sprint over the weekend. I'm challenged to find proper
superlatives to express my admiration.
Thank you, all of you, and please know that each of your contributions
are appreciated. Sorry for my "noise" on the list, but the activity is
phenomenal, noteworthy, and gratifying.
Paul
--
Hardware, n.:
The parts of a computer system that can be kicked.
next reply other threads:[~2021-02-01 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 8:42 Paul Simmons [this message]
2021-02-01 11:04 ` Michael Tremer
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=53e8ebef-ed82-d69e-5959-55b363499519@gmail.com \
--to=mbatranch@gmail.com \
--cc=development@lists.ipfire.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