From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] iprutils: update patches for the new version
Date: Thu, 18 Sep 2014 10:24:12 +0100 [thread overview]
Message-ID: <541AA4BC.6040608@imgtec.com> (raw)
In-Reply-To: <5419D5EA.6060602@zacarias.com.ar>
On 09/17/2014 07:41 PM, Gustavo Zacarias wrote:
> On 09/17/2014 02:19 PM, Vicente Olivert Riera wrote:
>
>> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>> ---
>> .../iprutils/iprutils-0001-Don-t-use-gettext.patch | 32 ++++++++++++++++++++
>> ...low-CFLAGS-to-be-extended-from-the-enviro.patch | 31 +++++++++++++++++++
>> .../iprutils/iprutils-01-dont-use-gettext.patch | 30 ------------------
>> .../iprutils-02-use-environment-cflags.patch | 20 ------------
>> 4 files changed, 63 insertions(+), 50 deletions(-)
>> create mode 100644 package/iprutils/iprutils-0001-Don-t-use-gettext.patch
>> create mode 100644 package/iprutils/iprutils-0002-Allow-CFLAGS-to-be-extended-from-the-enviro.patch
>> delete mode 100644 package/iprutils/iprutils-01-dont-use-gettext.patch
>> delete mode 100644 package/iprutils/iprutils-02-use-environment-cflags.patch
>
> Hi.
> The patch updates should be part of the first (bump) patch, otherwise
> it's just an extra commit that fixes breakage because the patches don't
> apply/work.
> It's like adding a new package that needs patches and said patches are
> part of a second patch ("these make it work for real").
> Regards.
>
Fixed. v2 patches sent.
--
Vincent
next prev parent reply other threads:[~2014-09-18 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 17:19 [Buildroot] [PATCH 1/3] iprutils: bump version to 2.4.2 Vicente Olivert Riera
2014-09-17 17:19 ` [Buildroot] [PATCH 2/3] iprutils: update patches for the new version Vicente Olivert Riera
2014-09-17 18:41 ` Gustavo Zacarias
2014-09-18 9:24 ` Vicente Olivert Riera [this message]
2014-09-17 17:19 ` [Buildroot] [PATCH 3/3] iprutils: Fix static build by passing the libraries in the right order Vicente Olivert Riera
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=541AA4BC.6040608@imgtec.com \
--to=vincent.riera@imgtec.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.