From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] automake: fix unescaped left brace warning patch.
Date: Thu, 9 Feb 2017 09:41:41 +0100 [thread overview]
Message-ID: <20170209094141.3fe22e82@free-electrons.com> (raw)
In-Reply-To: <20170209000710.13754-1-Adamduskett@outlook.com>
Hello,
On Wed, 8 Feb 2017 19:07:10 -0500, Adam Duskett wrote:
> .../0002-fix-unescaped-left-brace-warning.patch | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
> create mode 100644 package/automake/0002-fix-unescaped-left-brace-warning.patch
>
> diff --git a/package/automake/0002-fix-unescaped-left-brace-warning.patch b/package/automake/0002-fix-unescaped-left-brace-warning.patch
> new file mode 100644
> index 0000000..a33b1f1
> --- /dev/null
> +++ b/package/automake/0002-fix-unescaped-left-brace-warning.patch
> @@ -0,0 +1,19 @@
> +Automake currently has a unescaped left brace in it's automake.in folder
> +that generates the warning:
> +Unescaped left brace in regex is deprecated, passed through in regex;
> +This patch fixes this warning.
> +
> +Signed-off-by: Adam Duskett <aduskett@gmail.com>
I am *really* uncomfortable about merging patches touching the automake
code base if those patches are not upstream. So please submit this
upstream, and if it gets accepted, then we can integrate it in
Buildroot.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-09 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 0:07 [Buildroot] [PATCH 1/1] automake: fix unescaped left brace warning patch Adam Duskett
2017-02-09 8:41 ` Thomas Petazzoni [this message]
2017-02-09 12:33 ` Adam Duskett
2017-02-09 13:25 ` 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=20170209094141.3fe22e82@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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