From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current branch of OpenSSL 3
Date: Wed, 22 Mar 2023 09:30:09 +0000 [thread overview]
Message-ID: <2E56CF63-B772-4374-BE31-1E47C372F826@ipfire.org> (raw)
In-Reply-To: <7e0aec78-fe12-fe22-4fcc-ee0735a9893a@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
+1. Would like to review this, too!
-Michael
> On 21 Mar 2023, at 15:11, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Peter,
>
> You were going to provide me with your current branch of OpenSSL 3 so I can build it and test out OpenVPN with it to see if it causes anything to break on my configuration.
>
> Regards,
>
> Adolf.
>
> --
> Sent from my laptop
>
prev parent reply other threads:[~2023-03-22 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 15:11 Adolf Belka
2023-03-22 9:30 ` 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=2E56CF63-B772-4374-BE31-1E47C372F826@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