From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/python-cryptography: bump version to 2.3.1
Date: Sun, 19 Aug 2018 21:02:33 +0200 [thread overview]
Message-ID: <9fro4fx8c7.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: CAGm1_kvHG2zGtw8U200teJtVnjAOf57t_5XCxRsb3TsBjLi69Q@mail.gmail.com
Am Sun, 19 Aug 2018 20:53:49 +0200 schrieb Yegor Yefremov:
> Have you performed runtime tests?
Hi Yegor,
no, only build-tested with openssl-1.1.0i.
Regards, Bernd
next prev parent reply other threads:[~2018-08-19 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 18:42 [Buildroot] [PATCH/next 1/1] package/python-cryptography: bump version to 2.3.1 Bernd Kuhls
2018-08-19 18:53 ` Yegor Yefremov
2018-08-19 19:02 ` Bernd Kuhls [this message]
2018-08-20 8:05 ` Yegor Yefremov
2018-08-20 12:05 ` Yegor Yefremov
2018-09-10 21:39 ` Bernd Kuhls
2018-09-11 6:52 ` Yegor Yefremov
2018-08-29 20:20 ` Thomas Petazzoni
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=9fro4fx8c7.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.