From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Rename MySQL client package
Date: Mon, 20 Jan 2014 22:33:51 +0100 [thread overview]
Message-ID: <20140120213351.GD3421@free.fr> (raw)
In-Reply-To: <1390172539-5207-1-git-send-email-kuyurix@gmail.com>
Marcelo, All,
On 2014-01-19 23:02 +0000, Marcelo Guti?rrez spake thusly:
> From: "Marcelo Guti?rrez(UTN/FRH)" <kuyurix@gmail.com>
>
>
> Signed-off-by: Marcelo Guti?rrez(UTN/FRH) <kuyurix@gmail.com>
> ---
> Config.in.legacy | 7 +
> package/Config.in | 2 +-
> package/mysql/Config.in | 14 ++
> package/mysql/mysql-ac_cache_check.patch | 156 ++++++++++++++++++++
> package/mysql/mysql-configure-ps-cache-check.patch | 39 +++++
> package/mysql/mysql-use-new-readline-iface.patch | 21 +++
> package/mysql/mysql.mk | 48 ++++++
> 7 files changed, 286 insertions(+), 1 deletion(-)
> create mode 100644 package/mysql/Config.in
> create mode 100644 package/mysql/mysql-ac_cache_check.patch
> create mode 100644 package/mysql/mysql-configure-ps-cache-check.patch
> create mode 100644 package/mysql/mysql-use-new-readline-iface.patch
> create mode 100644 package/mysql/mysql.mk
Did you forget to rm the old mysql_client package, by chance? ;-)
Also, when sending mails, use the '-C -M' options: it will detect
renames and copies of files, and thus the diff will be much smaller.
It is even as smart as to detect a rename with modifications! :-)
> diff --git a/Config.in.legacy b/Config.in.legacy
> index 597534e..31fad3e 100644
> --- a/Config.in.legacy
> +++ b/Config.in.legacy
> @@ -112,6 +112,13 @@ config BR2_PACKAGE_LIBNFC_LLCP
> ###############################################################################
> comment "Legacy options removed in 2014.02"
>
> +config BR2_PACKAGE_MYSQL_CLIENT
> + bool "MySQL client renamed to MySQL"
> + select BR2_LEGACY
> + select BR2_PACKAGE_MYSQL
> + help
This needs to be: one leading tab, not spaces.
> + The option has been renamed BR2_PACKAGE_MYSQL
> +
Otherwise, this legacy entry is good! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-01-20 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 23:02 [Buildroot] [PATCH 1/2] Rename MySQL client package Marcelo Gutiérrez
2014-01-19 23:02 ` [Buildroot] [PATCH v3 2/2] add support for building the server Marcelo Gutiérrez
2014-01-20 21:44 ` Yann E. MORIN
2014-01-20 21:33 ` Yann E. MORIN [this message]
2014-01-20 21:45 ` [Buildroot] [PATCH 1/2] Rename MySQL client package Yann E. MORIN
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=20140120213351.GD3421@free.fr \
--to=yann.morin.1998@free.fr \
--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