From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/4] python: fix patch headers
Date: Mon, 8 Oct 2018 15:04:53 +0100 [thread overview]
Message-ID: <20181008140455.8990-2-ross.burton@intel.com> (raw)
In-Reply-To: <20181008140455.8990-1-ross.burton@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
---
.../0001-bpo-33354-Fix-test_ssl-when-a-filename-cannot-be-enc.patch | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/meta/recipes-devtools/python/python/0001-bpo-33354-Fix-test_ssl-when-a-filename-cannot-be-enc.patch b/meta/recipes-devtools/python/python/0001-bpo-33354-Fix-test_ssl-when-a-filename-cannot-be-enc.patch
index 776bbdcf7a4..4c0b3577b24 100644
--- a/meta/recipes-devtools/python/python/0001-bpo-33354-Fix-test_ssl-when-a-filename-cannot-be-enc.patch
+++ b/meta/recipes-devtools/python/python/0001-bpo-33354-Fix-test_ssl-when-a-filename-cannot-be-enc.patch
@@ -7,9 +7,7 @@ Subject: [PATCH] bpo-33354: Fix test_ssl when a filename cannot be encoded
Skip test_load_dh_params() of test_ssl when Python filesystem encoding
cannot encode the provided path.
-Upstream-Status:
-Backport[https://github.com/python/cpython/commit/19f6bd06af3c7fc0db5f96878aaa68f5589ff13e]
-
+Upstream-Status: Backport [https://github.com/python/cpython/commit/19f6bd06af3c7fc0db5f96878aaa68f5589ff13e]
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
Lib/test/test_ssl.py | 9 ++++++++-
--
2.11.0
next prev parent reply other threads:[~2018-10-08 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 14:04 [PATCH 1/4] gdb: fix patch headers Ross Burton
2018-10-08 14:04 ` Ross Burton [this message]
2018-10-08 14:04 ` [PATCH 3/4] python3: " Ross Burton
2018-10-08 14:04 ` [PATCH 4/4] lib11: " Ross Burton
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=20181008140455.8990-2-ross.burton@intel.com \
--to=ross.burton@intel.com \
--cc=openembedded-core@lists.openembedded.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