From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Core Update 2.12 Release Notes
Date: Wed, 27 Jun 2018 21:37:13 +0200 [thread overview]
Message-ID: <70d72085-f33f-e6df-c22d-4b7853389238@link38.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Hello Michael,
could you add two smaller changes to the release notes of 2.12 :
- Firewall GUI enhancements (by Alex, make grouping of IPsec subnets possible)
- Pakfire key rollover finished
Thanks, and best regards,
Peter Müller
P.S.: I hopefully will have some spare time to test this at the
weekend - along with a bunch of other things (rsyslog!). :-)
--
"We don't care. We don't have to. We're the Phone Company."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-06-27 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 19:37 Peter Müller [this message]
2018-06-28 12:28 ` Michael Tremer
2018-07-01 5:51 ` Peter Müller
2018-07-01 9:38 ` 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=70d72085-f33f-e6df-c22d-4b7853389238@link38.eu \
--to=peter.mueller@link38.eu \
--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