From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Core 136 released
Date: Sat, 12 Oct 2019 09:08:12 +0200 [thread overview]
Message-ID: <b97717c5-84ce-75b7-7b2c-813aa5e3ac79@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 292 bytes --]
Hi,
...I just noticed a typo/missing info on
https://blog.ipfire.org/post/ipfire-2-23-core-update-136-released ...: ;_)
Update packages:
'logrotate': should be version 3.*1*5.1
Addons:
'monit': is updated from version *3.23* (Release 10) to *3.25.3*
(Release 11)
jm2c ;-)
Best,
Matthias
next reply other threads:[~2019-10-12 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 7:08 Matthias Fischer [this message]
2019-10-13 13:14 ` 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=b97717c5-84ce-75b7-7b2c-813aa5e3ac79@ipfire.org \
--to=matthias.fischer@ipfire.org \
--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