From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] mariadb: needs dynamic library support
Date: Sun, 29 Jul 2018 15:20:40 +0200 [thread overview]
Message-ID: <20180729152040.08ef2756@windsurf> (raw)
In-Reply-To: <20180726163703.7598-2-bluemrp9@gmail.com>
Hello Ryan,
On Thu, 26 Jul 2018 09:37:02 -0700, Ryan Coe wrote:
> Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
> ---
> package/mysql/Config.in | 5 +++++
> 1 file changed, 5 insertions(+)
An empty commit log for this kind of change is really not good. How did
you realize it needs dynamic library support ? Why there is no
autobuilder failure ? How does it fail to build ?
I've improved the commit log and applied, but for future patches, it
would really be nice to have more detailed commit logs.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-29 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 16:37 [Buildroot] [PATCH v2 1/3] mariadb: move comments outside of define block Ryan Coe
2018-07-26 16:37 ` [Buildroot] [PATCH v2 2/3] mariadb: needs dynamic library support Ryan Coe
2018-07-29 13:20 ` Thomas Petazzoni [this message]
2018-08-23 20:18 ` Peter Korsgaard
2018-07-26 16:37 ` [Buildroot] [PATCH v2 3/3] mariadb: bump version to 10.2.16 Ryan Coe
2018-08-16 21:22 ` Thomas Petazzoni
2018-08-21 13:59 ` Ryan Coe
2018-08-21 15:35 ` Thomas Petazzoni
2018-07-29 13:19 ` [Buildroot] [PATCH v2 1/3] mariadb: move comments outside of define block Thomas Petazzoni
2018-08-23 20:15 ` Peter Korsgaard
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=20180729152040.08ef2756@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 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.