From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: yocto@yoctoproject.org
Cc: belen.barros.pena@linux.intel.com
Subject: [[PATCH][error-report-web] 0/8] Allow other type of errors and django 1.8
Date: Mon, 13 Jun 2016 18:32:08 -0500 [thread overview]
Message-ID: <1465860736-26581-1-git-send-email-anibal.limon@linux.intel.com> (raw)
The next patches enables support of django 1.8 LTS (two patches) and the other
are for enable to display other type of errors not only task related ones based
on design [1].
Also the changes could be reviewed at,
http://git.yoctoproject.org/cgit/cgit.cgi/error-report-web/log/?h=alimon/devel
[1] https://bugzilla.yoctoproject.org/attachment.cgi?id=3214
Aníbal Limón (8):
requirements.txt: Update requeriments for use 1.8 LTS Django version.
urls.py: RedirectView, fix warnings about change of default value in
django 1.9
Post/models.py: Increase the TASK field length
Post/migrations/0003_auto_20150603_0913.py: Replace tabs for spaces
Post/models.py: Build model add support for Error type.
Post/{models,parser}.py: Add support for receive/store error_type.
views/templates: Add support for display different type of errors
Post/{models,views}.py: Add FAILURE field on BuildFailure model
Post/migrations/0003_auto_20150603_0913.py | 6 +++---
Post/migrations/0004_auto_20160530_1126.py | 20 ++++++++++++++++++++
Post/migrations/0005_build_error_type.py | 19 +++++++++++++++++++
Post/migrations/0006_buildfailure_failure.py | 28 ++++++++++++++++++++++++++++
Post/models.py | 20 +++++++++++++++++++-
Post/parser.py | 17 ++++++++++++++---
Post/views.py | 17 ++++++-----------
project/urls.py | 4 ++--
requirements.txt | 2 +-
templates/error-details.html | 13 ++++++++++++-
templates/latest-errors.html | 16 ++++++++--------
11 files changed, 132 insertions(+), 30 deletions(-)
create mode 100644 Post/migrations/0004_auto_20160530_1126.py
create mode 100644 Post/migrations/0005_build_error_type.py
create mode 100644 Post/migrations/0006_buildfailure_failure.py
--
2.1.4
next reply other threads:[~2016-06-13 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 23:32 Aníbal Limón [this message]
2016-06-13 23:32 ` [[PATCH][error-report-web] 1/8] requirements.txt: Update requeriments for use 1.8 LTS Django version Aníbal Limón
2016-06-13 23:32 ` [[PATCH][error-report-web] 2/8] urls.py: RedirectView, fix warnings about change of default value in django 1.9 Aníbal Limón
2016-06-13 23:32 ` [[PATCH][error-report-web] 3/8] Post/models.py: Increase the TASK field length Aníbal Limón
2016-06-13 23:32 ` [[PATCH][error-report-web] 4/8] Post/migrations/0003_auto_20150603_0913.py: Replace tabs for spaces Aníbal Limón
2016-06-13 23:32 ` [[PATCH][error-report-web] 5/8] Post/models.py: Build model add support for Error type Aníbal Limón
2016-06-14 13:30 ` Michael Wood
2016-06-14 16:44 ` Aníbal Limón
2016-06-14 19:23 ` Aníbal Limón
2016-06-13 23:32 ` [[PATCH][error-report-web] 6/8] Post/{models, parser}.py: Add support for receive/store error_type Aníbal Limón
2016-06-13 23:32 ` [[PATCH][error-report-web] 7/8] views/templates: Add support for display different type of errors Aníbal Limón
2016-06-13 23:32 ` [[PATCH][error-report-web] 8/8] Post/{models, views}.py: Add FAILURE field on BuildFailure model Aníbal Limón
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=1465860736-26581-1-git-send-email-anibal.limon@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=belen.barros.pena@linux.intel.com \
--cc=yocto@yoctoproject.org \
/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.