From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Elizabeth 'pidge' Flanagan <pidge@toganlabs.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] report-error.bbclass: Add support for autosending
Date: Fri, 09 Sep 2016 08:42:25 +1200 [thread overview]
Message-ID: <1529433.MFaUV9yMeV@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <20160908092601.7588-1-pidge@toganlabs.com>
Hey Beth,
On Thu, 08 Sep 2016 11:26:01 Elizabeth 'pidge' Flanagan wrote:
> This commit pulls and extends the functionality of .oe-error-report into
> local.conf. It maintains the functionality of .oe-error-report.
>
> It also enables report-error to automatically send error reports to a
> specified error report server. This patch enables infrastructure ppl to
> set development teams up so that we can gather error metrics automatically.
>
> This relies on a new set of variables:
>
> REPORTERROR[autosend]="yes|no|ask"
> REPORTERROR[user]=username
> REPORTERROR[email]=email
> REPORTERROR[server]=error-report-web instance
>
> For autosend yes and no are pretty self explainatory. ask does not pass
> the -y flag to send-error-report, thus enabling the end user to review
> the report prior to submission.
I'm not sure if sentiment has changed on this issue (FWIW, it hasn't really
on my part), but this topic did come up before - start of thread here:
http://lists.openembedded.org/pipermail/openembedded-core/2014-March/090621.html
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2016-09-08 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 9:26 [RFC][PATCH] report-error.bbclass: Add support for autosending Elizabeth 'pidge' Flanagan
2016-09-08 18:23 ` Randy Witt
2016-09-08 20:42 ` Paul Eggleton [this message]
2016-09-08 22:01 ` Richard Purdie
2016-09-09 9:31 ` Martin Jansa
2016-09-09 9:38 ` Beth 'pidge' Flanagan
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=1529433.MFaUV9yMeV@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pidge@toganlabs.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