From: Paul Simmons <mbatranch@gmail.com>
To: development@lists.ipfire.org
Subject: Core 159 testing?
Date: Fri, 13 Aug 2021 12:24:05 -0500 [thread overview]
Message-ID: <d0f27ad7-28ff-b9e8-ba4e-06a3a1eebc62@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
"IPFire 2.27 - Core Update 159 Development Build: master" is no longer
in https://nightly.ipfire.org/master/latest/
Is there an ETA for Core 159 release? If so, I'll wait for it.
Thank you,
Paul
next reply other threads:[~2021-08-13 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 17:24 Paul Simmons [this message]
[not found] <26B5907F-97D2-456E-847B-F5DF7E543350@ipfire.org>
2021-08-13 18:28 ` Paul Simmons
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=d0f27ad7-28ff-b9e8-ba4e-06a3a1eebc62@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