Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3] busybox 1.18.1: add latest fix
Date: Wed, 12 Jan 2011 21:50:41 -0800	[thread overview]
Message-ID: <4D2E92B1.1000404@gmail.com> (raw)
In-Reply-To: <1294867230-7827-2-git-send-email-eric@eukrea.com>

On 1/12/2011 1:20 PM, Eric Bénard wrote:
> * httpd: send correct mtime for .gz filesmaster
> * patch fetched from git as per blindvt request
>
> Signed-off-by: Eric Bénard<eric@eukrea.com>

Acked-by: Khem Raj <raj.khem@gmail.com>
> ---
>   recipes/busybox/busybox_1.18.1.bb |    7 ++++---
>   1 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/recipes/busybox/busybox_1.18.1.bb b/recipes/busybox/busybox_1.18.1.bb
> index a2b4475..f337eef 100644
> --- a/recipes/busybox/busybox_1.18.1.bb
> +++ b/recipes/busybox/busybox_1.18.1.bb
> @@ -1,5 +1,5 @@
>   require busybox_1.1x.inc
> -PR = "${INC_PR}.4"
> +PR = "${INC_PR}.5"
>
>   SRC_URI += " \
>   	file://busybox-1.18.1-hush.patch \
> @@ -8,9 +8,10 @@ SRC_URI += " \
>   	file://busybox-1.18.1-mkswap.patch \
>   	file://busybox-1.18.1-warning.patch \
>   	file://busybox-1.18.1-modprobe-small.patch \
> -	file://busybox-1.18.1-tftp.patch \
> +	http://git.busybox.net/busybox/patch/id=8030a1484917d5b71d5ccd1a1d28a29da7a3d7f0;apply=yes;name=bb181-01 \
>   	"
>
>   SRC_URI[md5sum] = "f15fe752d8b7012aa5e59f83b88ccb1c"
>   SRC_URI[sha256sum] = "33eb25ea7b20c727c3af769256b21408a1ac1f927ff9f89a1f1e3767c18c9967"
> -
> +SRC_URI[bb181-01.md5sum] = "fe58a0e758c2581fdd2554186089b03b"
> +SRC_URI[bb181-01.sha256sum] = "f776d0b4ba525c62abe5e91f1432773eca92904cdecbdf48546a9271166cd896"




  parent reply	other threads:[~2011-01-13  5:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12 21:20 [PATCH 1/3] strace: add patch allowing compilation with kernel headers >= 2.6.32 Eric Bénard
2011-01-12 21:20 ` [PATCH 2/3] busybox 1.18.1: add latest fix Eric Bénard
2011-01-12 21:20   ` [PATCH 3/3] mtd-utils: add 1.4.1 Eric Bénard
2011-01-13  0:31     ` Tom Rini
2011-01-13 13:07       ` Eric Bénard
2011-01-13 13:54         ` Enrico Scholz
2011-01-13 14:31           ` Eric Bénard
2011-01-13 14:33             ` [PATCH v2] " Eric Bénard
2011-01-13 15:15               ` Tom Rini
2011-01-14  3:26               ` Khem Raj
2011-01-14 10:23                 ` Martin Jansa
2011-01-13  5:52     ` [PATCH 3/3] " Khem Raj
2011-01-13  5:50   ` Khem Raj [this message]
2011-01-13  0:30 ` [PATCH 1/3] strace: add patch allowing compilation with kernel headers >= 2.6.32 Tom Rini
2011-01-13  7:39   ` Eric Bénard
2011-01-13 15:13     ` Tom Rini
2011-01-13 15:17       ` Eric Bénard
2011-01-13  5:49 ` Khem Raj
2011-01-13  7:39   ` Eric Bénard
2011-01-13 13:45   ` [PATCH v2] " Eric Bénard
2011-01-13 15:15     ` Tom Rini
2011-01-13 15:29       ` Eric Bénard
2011-01-13 20:34       ` [PATCH] strace 4.5.20: stable since 04/14/2010 so remove DP=-1 Eric Bénard
2011-01-13 21:06         ` Tom Rini
2011-01-13 21:15           ` [PATCH v2] " Eric Bénard
2011-01-13 21:29             ` Tom Rini
2011-01-14  3:30             ` Khem Raj
2011-01-14  3:28       ` [PATCH v2] strace: add patch allowing compilation with kernel headers >= 2.6.32 Khem Raj
2011-01-14  3:15     ` Khem Raj

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=4D2E92B1.1000404@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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