All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: John Snow <jsnow@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Peter Krempa" <pkrempa@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH v4 2/2] GitLab: Add "Feature Request" issue template.
Date: Tue, 08 Jun 2021 14:59:16 +0100	[thread overview]
Message-ID: <87lf7klama.fsf@linaro.org> (raw)
In-Reply-To: <20210607153155.1760158-3-jsnow@redhat.com>


John Snow <jsnow@redhat.com> writes:

> Based on Peter Krempa's libvirt template, feature.md.
>
> CC: Peter Krempa <pkrempa@redhat.com>
> Signed-off-by: John Snow <jsnow@redhat.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> ---
>  .gitlab/issue_templates/feature_request.md | 32 ++++++++++++++++++++++
>  1 file changed, 32 insertions(+)
>  create mode 100644 .gitlab/issue_templates/feature_request.md
>
> diff --git a/.gitlab/issue_templates/feature_request.md b/.gitlab/issue_templates/feature_request.md
> new file mode 100644
> index 0000000000..fc58ca2763
> --- /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 -->?

Either way:

Reviewed-by: Alex Bennée <alex.bennee@linaro.org>


> +
> +
> +<!--
> +The line below ensures that proper tags are added to the issue.
> +Please do not remove it.
> +-->
> +/label ~"kind::Feature Request"


-- 
Alex Bennée


  reply	other threads:[~2021-06-08 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 15:31 [PATCH v4 0/2] Gitlab: Add issue templates John Snow
2021-06-07 15:31 ` [PATCH v4 1/2] GitLab: Add "Bug" issue reporting template John Snow
2021-06-08 13:57   ` Alex Bennée
2021-06-07 15:31 ` [PATCH v4 2/2] GitLab: Add "Feature Request" issue template John Snow
2021-06-08 13:59   ` Alex Bennée [this message]
2021-06-08 14:25     ` John Snow
2021-06-08  8:33 ` [PATCH v4 0/2] Gitlab: Add issue templates Stefan Hajnoczi
2021-06-15  0:03 ` John Snow
2021-06-15  8:26   ` Thomas Huth
2021-06-22 13:22     ` John Snow
2021-06-23  9:25 ` Alex Bennée

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=87lf7klama.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@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 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.