summaryrefslogtreecommitdiff
path: root/ext/pybind11/ISSUE_TEMPLATE.md
diff options
context:
space:
mode:
authorJason Lowe-Power <jason@lowepower.com>2017-11-17 17:02:05 -0800
committerJason Lowe-Power <jason@lowepower.com>2017-12-14 00:27:59 +0000
commitf07d5069d86e31ecf195664850f79fb00c445bd3 (patch)
treef54ac06896fa828f873d199a0e9b25bd94911c79 /ext/pybind11/ISSUE_TEMPLATE.md
parent3f64b374c49491f18dc2ca538ed8c8597e4aac83 (diff)
downloadgem5-f07d5069d86e31ecf195664850f79fb00c445bd3.tar.xz
ext: Upgrade PyBind11 to version 2.2.1
This upgrade is necessary for pybind to build with GCC 7.2. We still need to add the patch for stl.h. MSC_FULL_VER change is no longer needed. See https://gem5-review.googlesource.com/c/public/gem5/+/2230 Change-Id: I806729217d022070583994c2dfcaa74476aef30f Signed-off-by: Jason Lowe-Power <jason@lowepower.com> Reviewed-on: https://gem5-review.googlesource.com/5801 Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com> Maintainer: Andreas Sandberg <andreas.sandberg@arm.com>
Diffstat (limited to 'ext/pybind11/ISSUE_TEMPLATE.md')
-rw-r--r--ext/pybind11/ISSUE_TEMPLATE.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/ext/pybind11/ISSUE_TEMPLATE.md b/ext/pybind11/ISSUE_TEMPLATE.md
index 2e5f920f8..75df39981 100644
--- a/ext/pybind11/ISSUE_TEMPLATE.md
+++ b/ext/pybind11/ISSUE_TEMPLATE.md
@@ -1,5 +1,4 @@
Make sure you've completed the following steps before submitting your issue -- thank you!
-You can remove this template text afterward.
1. Check if your question has already been answered in the [FAQ](http://pybind11.readthedocs.io/en/latest/faq.html) section.
2. Make sure you've read the [documentation](http://pybind11.readthedocs.io/en/latest/). Your issue may be addressed there.
@@ -7,11 +6,12 @@ You can remove this template text afterward.
4. If you have a genuine bug report or a more complex question which is not answered in the previous items (or not suitable for chat), please fill in the details below.
5. Include a self-contained and minimal piece of code that reproduces the problem. If that's not possible, try to make the description as clear as possible.
+*After reading, remove this checklist and the template text in parentheses below.*
-#### Issue description
+## Issue description
(Provide a short description, state the expected behavior and what actually happens.)
-#### Reproducible example code
+## Reproducible example code
(The code should be minimal, have no external dependencies, isolate the function(s) that cause breakage. Submit matched and complete C++ and Python snippets that can be easily compiled and run to diagnose the issue.)