From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/5] python-sqlalchemy: new package
Date: Sat, 10 Feb 2018 16:21:44 +0100 [thread overview]
Message-ID: <20180210162144.1784769f@windsurf.lan> (raw)
In-Reply-To: <20180206132506.30389-2-aduskett@gmail.com>
Hello,
Thanks for this contribution.
On Tue, 6 Feb 2018 08:25:03 -0500, Adam Duskett wrote:
> SQLAlchemy is the Python SQL toolkit and Object Relational Mapper that gives
> application developers the full power and flexibility of SQL.
>
> It provides a full suite of well known enterprise-level persistence patterns,
> designed for efficient and high-performing database access, adapted into a
> simple and Pythonic domain language.
>
> Signed-off-by: Adam Duskett <aduskett@gmail.com>
It would be nice to run check-package before submitting packages:
$ ./utils/check-package package/python-sqlalchemy/*
package/python-sqlalchemy/Config.in:2: should be indented with one tab (http://nightly.buildroot.org/#_config_files)
package/python-sqlalchemy/Config.in:3: should be indented with one tab (http://nightly.buildroot.org/#_config_files)
package/python-sqlalchemy/Config.in:4: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
package/python-sqlalchemy/Config.in:5: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
package/python-sqlalchemy/Config.in:6: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
package/python-sqlalchemy/Config.in:8: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
package/python-sqlalchemy/Config.in:9: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
package/python-sqlalchemy/Config.in:10: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
package/python-sqlalchemy/Config.in:11: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in)
31 lines processed
9 warnings generated
I've fixed those issues and applied to next. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-10 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 13:25 [Buildroot] [PATCH v2 1/5] python-psycopg2: new package Adam Duskett
2018-02-06 13:25 ` [Buildroot] [PATCH v2 2/5] python-sqlalchemy: " Adam Duskett
2018-02-06 13:38 ` Yegor Yefremov
2018-02-10 15:21 ` Thomas Petazzoni [this message]
2018-02-06 13:25 ` [Buildroot] [PATCH v2 3/5] python-flask-sqlalchemy: " Adam Duskett
2018-02-06 13:37 ` Yegor Yefremov
2018-02-10 15:28 ` Thomas Petazzoni
2018-02-06 13:25 ` [Buildroot] [PATCH v2 4/5] python-visitor: " Adam Duskett
2018-02-06 13:37 ` Yegor Yefremov
2018-04-27 21:27 ` Thomas Petazzoni
2018-02-06 13:25 ` [Buildroot] [PATCH v2 5/5] python-flask-bootstrap: " Adam Duskett
2018-02-06 13:37 ` Yegor Yefremov
2018-04-27 21:33 ` Thomas Petazzoni
2018-04-28 5:15 ` Yegor Yefremov
2018-04-28 10:17 ` Thomas Petazzoni
2018-05-02 9:37 ` Yegor Yefremov
2018-09-16 20:05 ` Thomas Petazzoni
2018-02-10 15:22 ` [Buildroot] [PATCH v2 1/5] python-psycopg2: " Thomas Petazzoni
2018-02-10 17:40 ` Yegor Yefremov
2018-02-12 12:06 ` Adam Duskett
2018-02-12 13:48 ` Thomas Petazzoni
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=20180210162144.1784769f@windsurf.lan \
--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 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.