From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 2.12 Release Notes
Date: Sun, 01 Jul 2018 10:38:03 +0100 [thread overview]
Message-ID: <75a2f4b9f0ccdc34b949a5069590e01c361e61ea.camel@ipfire.org> (raw)
In-Reply-To: <4ac3cab4-17f3-a20a-3039-f6494db2c8b3@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Sun, 2018-07-01 at 07:51 +0200, Peter Müller wrote:
> Hello,
>
> > On Wed, 2018-06-27 at 21:37 +0200, Peter Müller wrote:
> > > 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
> >
> > This, technically, is not finished because the server still signs all files
> > with
> > the old key.
> >
> > I didn't have time yet to update the scripts.
>
> I see. Are you planning to do so before releasing the Core Update?
I was, but cannot guarantee it since I have a lot of stuff going on at the
moment.
- -Michael
>
> Best regards,
> Peter Müller
> >
> > > 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!). :-)
>
>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAls4oPsACgkQgHnw/2+Q
CQeHFQ//bV4e66SaqA5G65cVzow1XIgCPVLPJyX4zbPMWXImKahxurD4r31HBBEQ
AXyGQOpgofrAbb6V/8YhdOVCt5lv1D0MUI0uBPmboMOtvWx9RZA9fRlzaWyP6Z4R
PxtSsizW87QPY90STs0a9cofhB+YLD5/BilrhCCkyfBnUZNnYCMuC4p/XTl1U7Jo
IE8Lr5jUUtqoS6kQIM5GaPe3TU0By57UgbyRkPG/UWMtshqKIYGdb8uyaUiljDNg
YQ2vaSsqFrMDGPH5fj8KMkBTNuIsHiq+fFa8UgKT4HVBNWSnTj/zV7H4ML4ha9fG
eDg/ObUxmQsMDSg08L9XRyYQ+fDxNonlvPYSjh2ApCX3eSuID9NE1Fg9RVGl47dz
eB0DaOl5CbAdqAnUIAW+c8Dd4gZLxvQRi/yMXxitiFh2vHTqfr7MK6uMjZdrTAs8
3aKsPCn+UiNXE5cFHBioG5sZv/fnsa09bXrwS/u2JPg0xRmB3TMzZfkrEonMdDxv
scNF16sJZLxNsglFh9/Pj8H8klCHqvQI7/bcNf+qrTesy3NY+3B3+jO7PxUDfoCr
v4Tkg7aV7f0oiqIzukGnoGTzaiNJ7wlBnnve4P+g+CXmWoEdTP7cQcf/hNGN6h0Z
P7TTXL/TtHnKIBqc3+4B1DWS/+ylfK1JWc0+ZZwmpE2mqYIJSDM=
=zlsr
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-07-01 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 19:37 Peter Müller
2018-06-28 12:28 ` Michael Tremer
2018-07-01 5:51 ` Peter Müller
2018-07-01 9:38 ` Michael Tremer [this message]
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=75a2f4b9f0ccdc34b949a5069590e01c361e61ea.camel@ipfire.org \
--to=michael.tremer@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