public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: [PATCH] download ET IDS rules via HTTPS
Date: Wed, 15 Aug 2018 16:57:42 +0200	[thread overview]
Message-ID: <79eebfb0-50c0-215f-2822-994610742b80@link38.eu> (raw)
In-Reply-To: <bc1de8bfe8ec81bb04b762509ade136c649003e3.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

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.

Thanks, and best regards,
Peter Müller
- -- 
"We don't care.  We don't have to.  We're the Phone Company."
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEvP4SiGhEYDJyrRLk2UjyD317n2gFAlt0P2UACgkQ2UjyD317
n2gm/xAAqFNT6RprcdyGVJHDtf2cgQNyf4SrLkgQxKmIXDG02G/8GHx35vwi2mHT
gAL884a8pjANVgD39zfyyhLRdAtp25hrtWTixz7LnisyMO66yTwtUNTDBGeA5BfK
qKxOrQbZoRkYwmoJI63KDmqR6RrmgWaVQE9v4jaV76IcQP93zE+ehk4CfW/JJrPJ
W4aBw45AL6hGIDuShp1FdKhvZ7VNqIbrxmMzd34p5eLil2ZlRcvp3Gsac98coXMY
UP85k+/uLcO5iSKkT8kHjdVD+dE/REjsXpcXvdV53Qy/a4DenAKRCEtdccU2HmhT
su8MwtxgrqOz8pVd0Cq4ZVEoR6RN55Y/6MWfdwSvoS4WcxzQJ7LE1ilK5zS7qYhW
m8TwyM0ItLW05WlI/CRfpqLJ1r5Wcz4KiXxn/o4lC+Yo5EC3Z1qqKJXSibFEd6os
xBOZ7YxZQe85xr4gRpdH5T71ugTDsgUJipeBMqH7jk6lpPTP4ZYl+qZbI+PND7SG
xEQOBV69FLIhw+nzgyH1ECAT/fsTPxBVWE9q5LFu6u29p102kO7rElvzfo0lfjXs
FK0dRlzzNWX3EzCOLE37bSo7nN7jVWXfTLnjIsP9nm86+b96YHpHJtGC8NdWw6hi
kb3HjLseuJEg3SUCp87s5+t4AEnUaTSe6W0BM/2ZmrwsB0sGsqI=
=VYpy
-----END PGP SIGNATURE-----

  reply	other threads:[~2018-08-15 14:57 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 [this message]
2018-08-16 12:40     ` 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=79eebfb0-50c0-215f-2822-994610742b80@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