From: Ryan Coe <bluemrp9@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/3] package/mariadb: update startup scripts
Date: Mon, 16 Dec 2019 16:03:49 -0800 [thread overview]
Message-ID: <145ed763-08f3-c71d-e306-8b16586d6f1d@gmail.com> (raw)
In-Reply-To: <20191216093535.08ca160d@windsurf.home>
Thomas,
On 12/16/19 12:35 AM, Thomas Petazzoni wrote:
> Hello,
>
> On Sun, 15 Dec 2019 13:33:25 -0800
> Ryan Coe <bluemrp9@gmail.com> wrote:
>
>> The init scripts have been modified to create a directory under
>> /var/log/mysql and specify mysqld to use it for logging. The directory
>> test to call mysql_install_db has been redirected to /dev/null to prevent
>> an error message from showing if /var/lib/mysql does not exist.
>>
>> Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
> A commit title that says "update startup scripts" is a good hint that
> the splitting of changes is not good. It hints that you're doing
> several things at once in the same commit, which are unrelated to each
> other.
>
> There are (at least?) three independent changes here:
>
> - Redirection of stderr when listing $MYSQL_LIB
>
> - Rename of the MYSQL_PID variable
>
> - Move the logs to /var/log/mysql
>
> Three independent changes should lead to three independent commits.
I will re-submit.
>
> Thanks!
>
> Thomas
next prev parent reply other threads:[~2019-12-17 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 21:33 [Buildroot] [PATCH v2 1/3] package/mariadb: bump version to 10.4.11 Ryan Coe
2019-12-15 21:33 ` [Buildroot] [PATCH v2 2/3] package/mariadb: update startup scripts Ryan Coe
2019-12-16 8:35 ` Thomas Petazzoni
2019-12-17 0:03 ` Ryan Coe [this message]
2019-12-15 21:33 ` [Buildroot] [PATCH v2 3/3] package/mariadb: prefix sysroot in mariadb_config Ryan Coe
2019-12-17 0:38 ` Ryan Coe
2019-12-17 7:58 ` Thomas Petazzoni
2019-12-16 8:33 ` [Buildroot] [PATCH v2 1/3] package/mariadb: bump version to 10.4.11 Thomas Petazzoni
2019-12-17 0:12 ` Ryan Coe
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=145ed763-08f3-c71d-e306-8b16586d6f1d@gmail.com \
--to=bluemrp9@gmail.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.