From: Saul Wold <sgw@linux.intel.com>
To: Valentin Popa <valentin.popa@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] lighttpd: upgrade to 1.4.33
Date: Thu, 14 Nov 2013 09:37:43 -0800 [thread overview]
Message-ID: <52850A67.7080701@linux.intel.com> (raw)
In-Reply-To: <1384440781-12525-1-git-send-email-valentin.popa@intel.com>
On 11/14/2013 06:53 AM, Valentin Popa wrote:
> Signed-off-by: Valentin Popa <valentin.popa@intel.com>
> ---
> .../lighttpd/{lighttpd_1.4.32.bb => lighttpd_1.4.33.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-extended/lighttpd/{lighttpd_1.4.32.bb => lighttpd_1.4.33.bb} (93%)
>
Can you please do the patch directory rename as I have suggested, files
-> lighttpd.
Thanks
Sau!
> diff --git a/meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb b/meta/recipes-extended/lighttpd/lighttpd_1.4.33.bb
> similarity index 93%
> rename from meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb
> rename to meta/recipes-extended/lighttpd/lighttpd_1.4.33.bb
> index a1f0589..e8be659 100644
> --- a/meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb
> +++ b/meta/recipes-extended/lighttpd/lighttpd_1.4.33.bb
> @@ -24,8 +24,8 @@ SRC_URI = "http://download.lighttpd.net/lighttpd/releases-1.4.x/lighttpd-${PV}.t
> file://lighttpd.service \
> "
>
> -SRC_URI[md5sum] = "8e2d4ae8e918d4de1aeb9842584d170b"
> -SRC_URI[sha256sum] = "60691b2dcf3ad2472c06b23d75eb0c164bf48a08a630ed3f308f61319104701f"
> +SRC_URI[md5sum] = "e66b8164e5fc5a6beec0823b697fbe1d"
> +SRC_URI[sha256sum] = "2ff2324658c0f90e7d39afd40f08f11ca230903b9019c31a2bbecd8f087f235e"
>
> EXTRA_OECONF = " \
> --without-bzip2 \
>
prev parent reply other threads:[~2013-11-14 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 14:53 [PATCH] lighttpd: upgrade to 1.4.33 Valentin Popa
2013-11-14 17:37 ` Saul Wold [this message]
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=52850A67.7080701@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=valentin.popa@intel.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 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.