From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Peter Krempa" <pkrempa@redhat.com>,
"John Snow" <jsnow@redhat.com>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PULL 5/7] GitLab: Add "Feature Request" issue template.
Date: Fri, 25 Jun 2021 10:13:53 +0100 [thread overview]
Message-ID: <20210625091355.25673-6-alex.bennee@linaro.org> (raw)
In-Reply-To: <20210625091355.25673-1-alex.bennee@linaro.org>
From: John Snow <jsnow@redhat.com>
Based on Peter Krempa's libvirt template, feature.md.
Signed-off-by: John Snow <jsnow@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
CC: Peter Krempa <pkrempa@redhat.com>
Message-Id: <20210607153155.1760158-3-jsnow@redhat.com>
Message-Id: <20210623102749.25686-6-alex.bennee@linaro.org>
diff --git a/.gitlab/issue_templates/feature_request.md b/.gitlab/issue_templates/feature_request.md
new file mode 100644
index 0000000000..7de02dcc2c
--- /dev/null
+++ b/.gitlab/issue_templates/feature_request.md
@@ -0,0 +1,32 @@
+<!--
+This is the upstream QEMU issue tracker.
+
+Please note that QEMU, like most open source projects, relies on
+contributors who have motivation, skills and available time to work on
+implementing particular features.
+
+Feature requests can be helpful for determining demand and interest, but
+they are not a guarantee that a contributor will volunteer to implement
+it. We welcome and encourage even draft patches to implement a feature
+be sent to the mailing list where it can be discussed and developed
+further by the community.
+
+Thank you for your interest in helping us to make QEMU better!
+-->
+
+## Goal
+<!-- Describe the final result you want to achieve. Avoid design specifics. -->
+
+
+## Technical details
+<!-- Describe technical details, design specifics, suggestions, versions, etc. -->
+
+
+## Additional information
+<!-- Patch or branch references, any other useful information -->
+
+<!--
+The line below ensures that proper tags are added to the issue.
+Please do not remove it.
+-->
+/label ~"kind::Feature Request"
--
2.20.1
next prev parent reply other threads:[~2021-06-25 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 9:13 [PULL 0/7] misc fixes (docs, plugins, tests) Alex Bennée
2021-06-25 9:13 ` [PULL 1/7] tests/acceptance: tweak the tcg/kvm tests for virt Alex Bennée
2021-06-25 9:13 ` [PULL 2/7] docs/devel: Add a single top-level header to MTTCG's doc Alex Bennée
2021-06-25 9:13 ` [PULL 3/7] scripts/checkpatch: roll diff tweaking into checkpatch itself Alex Bennée
2021-06-25 9:13 ` [PULL 4/7] GitLab: Add "Bug" issue reporting template Alex Bennée
2021-06-25 9:13 ` Alex Bennée [this message]
2021-06-25 9:13 ` [PULL 6/7] tests/tcg: skip the signals test for hppa/s390x for now Alex Bennée
2021-09-11 21:57 ` Philippe Mathieu-Daudé
2021-06-25 9:13 ` [PULL 7/7] plugins/api: expose symbol lookup to plugins Alex Bennée
2021-06-25 14:28 ` [PULL 0/7] misc fixes (docs, plugins, tests) Peter Maydell
2021-06-25 18:39 ` Peter Maydell
2021-06-28 17:42 ` Peter Maydell
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=20210625091355.25673-6-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).