Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] busybox: Upgrade to v1.21.0
Date: Mon, 01 Apr 2013 11:41:46 +0300	[thread overview]
Message-ID: <5159484A.1020603@intel.com> (raw)
In-Reply-To: <20130329170003.GA7125@mx.loc>


On 03/29/2013 07:00 PM, Bernhard Reutner-Fischer wrote:
> On Fri, Mar 29, 2013 at 12:05:10PM +0200, Radu Moisan wrote:
>> Removed obsolete patches
>> Added a few new patches pending 1.21.1
>> *busybox-1.21.0-mdev.patch
>> *busybox-1.21.0-platform.patch
>> *busybox-1.21.0-xz.patch
>>
>> Signed-off-by: Radu Moisan <radu.moisan@intel.com>
>> ---
>> .../busybox-1.20.2/busybox-1.20.2-kernel_ver.patch |   28 -
>> .../busybox-mkfs-minix-tests_bigendian.patch       |   34 --
>> .../fix-for-spurious-testsuite-failure.patch       |   27 -
>> .../busybox/busybox-1.20.2/sys_resource.patch      |   99 ---
>> .../busybox/busybox-1.20.2/wget_dl_dir_fix.patch   |   30 -
>> .../B921600.patch                                  |    0
>> .../busybox-1.21.0/busybox-1.21.0-mdev.patch       |  643 ++++++++++++++++++++
>> .../busybox-1.21.0/busybox-1.21.0-platform.patch   |   24 +
>> .../busybox/busybox-1.21.0/busybox-1.21.0-xz.patch |   84 +++
>> .../busybox-appletlib-dependency.patch             |    0
>> .../busybox-udhcpc-no_deconfig.patch               |    0
>> .../{busybox-1.20.2 => busybox-1.21.0}/defconfig   |    0
>> .../get_header_tar.patch                           |    0
>> .../run-parts.in.usr-bin.patch                     |    6 +-
>> .../stat-usr-bin.patch                             |    0
>> ...estsuite-du-du-k-works-fix-false-positive.patch |    0
>> .../watch.in.usr-bin.patch                         |    0
>> .../{busybox_1.20.2.bb => busybox_1.21.0.bb}       |   17 +-
>> 18 files changed, 762 insertions(+), 230 deletions(-)
>> delete mode 100644 meta/recipes-core/busybox/busybox-1.20.2/busybox-1.20.2-kernel_ver.patch
>> delete mode 100644 meta/recipes-core/busybox/busybox-1.20.2/busybox-mkfs-minix-tests_bigendian.patch
>> delete mode 100644 meta/recipes-core/busybox/busybox-1.20.2/fix-for-spurious-testsuite-failure.patch
>> delete mode 100644 meta/recipes-core/busybox/busybox-1.20.2/sys_resource.patch
>> delete mode 100644 meta/recipes-core/busybox/busybox-1.20.2/wget_dl_dir_fix.patch
>> rename meta/recipes-core/busybox/{busybox-1.20.2 => busybox-1.21.0}/B921600.patch (100%)
> I wonder how this applies without fuzz as
> it was applied upstream back in 2009:
> http://git.busybox.net/busybox/commit/?id=e707a3000b2f6e2f684b6e85cd60590318d157c4

Many patches apply with some fuzz, and that's fine as log as it applies 
and keeps fixing something. However this one may not be necessary to 
carry along indeed. I'll look into it and drop, same for 
busybox-appletlib-dependency.patch if applied upstream.

Radu



  reply	other threads:[~2013-04-01  8:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29 10:05 [PATCH v2] busybox: Upgrade to v1.21.0 Radu Moisan
2013-03-29 13:30 ` Radu Moisan
2013-03-29 17:00 ` Bernhard Reutner-Fischer
2013-04-01  8:41   ` Radu Moisan [this message]
2013-04-01  8:58   ` Radu Moisan

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=5159484A.1020603@intel.com \
    --to=radu.moisan@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rep.dot.nop@gmail.com \
    /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