qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Peter Krempa" <pkrempa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template
Date: Thu, 3 Jun 2021 21:35:47 +0100	[thread overview]
Message-ID: <YLk9C3Nbod2Xj1qK@redhat.com> (raw)
In-Reply-To: <ae5c5066-cefc-1a29-9729-d0bafae5c8f5@redhat.com>

On Thu, Jun 03, 2021 at 03:11:28PM -0400, John Snow wrote:
> On 6/3/21 3:26 AM, Philippe Mathieu-Daudé wrote:
> > I haven't reviewed earlier version, but I wonder about the "build from
> > sources" use case (this is not a template for distributions but for the
> > mainstream project), so maybe add:
> > 
> >    ## Build environment (in case you built QEMU from source)
> >    - configure script command line: (e.g. ./configure --enable-nettle
> > --disable-glusterfs --disable-user)
> >    - configure script summary output
> 
> Maybe just a little bit too much information. Even though I am pushing
> people to build from source, I actually think more reports are likely not to
> have done so.

We need to bear in mind what % of bug reports do we actually need
this information for.  We don't want to be asking for information
that we know is going to be irrelevant for (say) 60% of bug reports,
because that wastes time of users.

My gut feeling is that while configure args are useful to know in
many cases, I doubt it genuinely needed for more than a relatively
small percentage of bug reports.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-06-03 20:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  0:11 [PATCH v3 0/2] Gitlab: Add issue templates John Snow
2021-06-03  0:11 ` [PATCH v3 1/2] GitLab: Add "Bug" issue reporting template John Snow
2021-06-03  5:15   ` Thomas Huth
2021-06-03  7:26   ` Philippe Mathieu-Daudé
2021-06-03 19:11     ` John Snow
2021-06-03 20:35       ` Daniel P. Berrangé [this message]
2021-06-03  8:45   ` Stefan Hajnoczi
2021-06-03  9:20     ` Daniel P. Berrangé
2021-06-03 11:52       ` Stefan Hajnoczi
2021-06-03 14:12         ` John Snow
2021-06-03 14:44       ` John Snow
2021-06-03 14:57         ` Daniel P. Berrangé
2021-06-03  0:11 ` [PATCH v3 2/2] GitLab: Add "Feature Request" issue template John Snow
2021-06-03  5:16   ` Thomas Huth
2021-06-03  7:15 ` [PATCH v3 0/2] Gitlab: Add issue templates Philippe Mathieu-Daudé

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=YLk9C3Nbod2Xj1qK@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --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).