From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] download ET IDS rules via HTTPS
Date: Thu, 16 Aug 2018 13:40:23 +0100 [thread overview]
Message-ID: <51a5b60a4c164dd2332c654020c60a6f3432a8f1.camel@ipfire.org> (raw)
In-Reply-To: <79eebfb0-50c0-215f-2822-994610742b80@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Wed, 2018-08-15 at 16:57 +0200, Peter Müller wrote:
> Hello Michael,
>
> thanks for the hint.
>
> These linewraps did not occur again after switching to inline
> PGP signatures, so I suspect it was because of a bug in PGP/MIME
> implementation of my MUA.
>
> Sorry for the delay. All affected patches were re-sent.
>
> Let me know if there is any trouble with them.
Yes there was. I responded on another email.
>
> Thanks, and best regards,
> Peter Müller
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAlt1cLcACgkQgHnw/2+Q
CQed5A/+OvTFprYCo6bzB49ek/BzM4xHfIyfTnu62nNfQYrUux5VmExRPdxZQhnd
woyAjBzI3cVNhU7NDHl+QrUbLbP56J77ZDVQDEmvLRbPjCf8WzngSLdlXhSR2UFI
pP4PK52uAeTcGqHHHd6CPlt2rSm7wJnaR2peEBTiNdwVFyfIiRboQnnGXtpg2kFB
BfPASTeJ/x6vMJ1Yy3cURNeD1ozS0ryCm/KJYJAZUvbFOVwd1xfeWxxHeJ/bRptG
4vLIZTGFgwfx/XBE+INhMoYFodvnSHA+ns6Nvt37D48sA7tr1wmNUuQav0dTaBe4
gZNaVpELqOMW1/0XubJFFceAE9A4AZw/SHOGlq3pgQ3CieVG916mRXX+WttgKmRR
EcReEARWJrJBt7igWOkdiLCYnf82eg/pq/CutIKvijdguIucfYT48JFk/pe8O6FC
BH40Bb7pZR8X/wVoeTq5Zskb4zmQr9XgKYTkSSA/gMA/yBb/PSK372FPCFr7WMcj
PqoUkCi2ebljJ26L5WofxNzmwMceCnHaPDXStGWVLh5X0dL96OBH7FEm4WpgH7G8
zaPgfmQmqctF3HGiFC2S5eey8lr72jcvrIg2cd8v5n5pb2nr+v8955qTGG4fg/NS
q/5Up82Ri3MtFP7S0kYt3D2dHhR7cOwPn9KnEPA85242I3lwz1Y=
=cs5l
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-08-16 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 9:50 Peter Müller
2018-08-13 20:06 ` Michael Tremer
2018-08-15 14:57 ` Peter Müller
2018-08-16 12:40 ` 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=51a5b60a4c164dd2332c654020c60a6f3432a8f1.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