Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] python-influxdb: new
Date: Mon, 30 Apr 2018 17:47:35 +0200	[thread overview]
Message-ID: <20180430174735.15bf267d@windsurf> (raw)
In-Reply-To: <20180430102117.27271-1-sven.haardiek@iotec-gmbh.de>

Hello Sven,

On Mon, 30 Apr 2018 12:21:17 +0200, Sven Haardiek wrote:
> InfluxDB client.
> 
> Signed-off-by: Sven Haardiek <sven.haardiek@iotec-gmbh.de>
> ---
>  package/Config.in                            |  1 +
>  package/python-influxdb/Config.in            | 10 ++++++++++
>  package/python-influxdb/python-influxdb.hash |  5 +++++
>  package/python-influxdb/python-influxdb.mk   | 14 ++++++++++++++
>  4 files changed, 30 insertions(+)
>  create mode 100644 package/python-influxdb/Config.in
>  create mode 100644 package/python-influxdb/python-influxdb.hash
>  create mode 100644 package/python-influxdb/python-influxdb.mk

Applied to master after fixing the commit title, and adding an entry in
the DEVELOPERS file.

It is worth mentioning that you now have two separate entries in the
DEVELOPERS file, each with a different e-mail address. Maybe you want
to check this and see if having two different entries make sense, or if
they should be merged together.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-04-30 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30 10:21 [Buildroot] [PATCH 1/1] python-influxdb: new Sven Haardiek
2018-04-30 11:08 ` Yegor Yefremov
2018-04-30 15:47 ` 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=20180430174735.15bf267d@windsurf \
    --to=thomas.petazzoni@bootlin.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