From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] python-raven: new package
Date: Wed, 22 Nov 2017 22:45:46 +0100 [thread overview]
Message-ID: <20171122224546.07eb63f4@windsurf.lan> (raw)
In-Reply-To: <20171109171417.30187-1-joseph.kogut@gmail.com>
Hello,
On Thu, 9 Nov 2017 09:14:17 -0800, Joseph Kogut wrote:
> Changes since v2:
> - remove newlines from Config.in
> - add LICENSE hash
>
> Changes since v1:
> - reword commit to match upstream style
> - fold the DEVELOPERS modifications into the same commit
> - add Config selections for required python core modules
> - bump version to 6.3.0
>
> Tested in a clean chroot, events are generated for exceptions, and
> reported to the server configured for the client.
>
> Signed-off-by: Joseph Kogut <joseph.kogut@gmail.com>
> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> package/python-raven/Config.in | 12 ++++++++++++
> package/python-raven/python-raven.hash | 5 +++++
> package/python-raven/python-raven.mk | 14 ++++++++++++++
> 5 files changed, 33 insertions(+)
> create mode 100644 package/python-raven/Config.in
> create mode 100644 package/python-raven/python-raven.hash
> create mode 100644 package/python-raven/python-raven.mk
Applied to next, thanks.
Also, thanks Yegor for the review!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-11-22 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171102163022.23953-1-joseph.kogut@gmail.com>
2017-11-09 1:55 ` [Buildroot] [PATCH v2 1/1] python-raven: new package Joseph Kogut
2017-11-09 6:27 ` Yegor Yefremov
2017-11-09 17:14 ` [Buildroot] [PATCH v3 " Joseph Kogut
2017-11-22 21:45 ` Thomas Petazzoni [this message]
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=20171122224546.07eb63f4@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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