From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: cu179 ETA?
Date: Fri, 22 Sep 2023 11:36:26 -0500 [thread overview]
Message-ID: <0ddca2d8-48eb-7575-7402-7ca8df8c8b27@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
Do we have a projected release date / time for CU179?
Thank you,
P
--
When I was a kid, I used to pray every night for a new bike. Then I realised, the Lord doesn't work that way. So I just stole one and asked Him to forgive me ... and I got it!
-- Emo Phillips
next reply other threads:[~2023-09-22 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 16:36 Paul Simmons [this message]
2023-09-22 19:10 ` jon
2023-09-22 19:25 ` Paul Simmons
2023-09-22 19:31 ` Adolf Belka
2023-09-25 8:45 ` 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=0ddca2d8-48eb-7575-7402-7ca8df8c8b27@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