From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 20/26] libiconv: Update to 1.14
Date: Tue, 29 Nov 2011 16:19:40 -0800 [thread overview]
Message-ID: <4ED5769C.2070905@linux.intel.com> (raw)
In-Reply-To: <4ED573D3.4040408@linux.intel.com>
On 29/11/11 16:07, Saul Wold wrote:
>>
>> where are checksums now?
>>
> Vanished!
>
> I did a fetch for all of these and did not see errors, will go back and
> fix these and the Xorg-server.
It's a NOTE not an ERROR. Maybe we should change that? Further, IIRC, if
the files are already in DL_DIR (with the we don't checksum them.
As the last person to touch that code I'm happy to be assignee of any
bug you may wish to file.
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-30 0:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 23:00 [PATCH 00/26] Various Package Updates Saul Wold
2011-11-29 23:00 ` [PATCH 01/26] wget: Update to 1.13.4 Saul Wold
2011-11-29 23:00 ` [PATCH 02/26] json-glib: Update to 0.14.2 Saul Wold
2011-11-29 23:00 ` [PATCH 03/26] libdrm: Update to 2.4.27 Saul Wold
2011-11-29 23:00 ` [PATCH 04/26] mkfontscale: Update to 1.0.9 Saul Wold
2011-11-29 23:00 ` [PATCH 05/26] xdpyinfo: Update to 1.3.0 Saul Wold
2011-11-29 23:00 ` [PATCH 06/26] xinit: Update to 1.3.1 Saul Wold
2011-12-09 18:42 ` Paul Menzel
2011-12-09 18:50 ` Mark Hatle
2011-12-09 19:01 ` Joshua Lock
2011-12-09 19:46 ` Khem Raj
2011-11-29 23:00 ` [PATCH 07/26] xkbcomp: Update to 1.2.3 Saul Wold
2011-11-29 23:00 ` [PATCH 08/26] xprop: Update to 1.2.1 Saul Wold
2011-11-29 23:00 ` [PATCH 09/26] xrandr: Update to 1.3.5 Saul Wold
2011-11-29 23:00 ` [PATCH 10/26] xset: Update to 1.2.2 Saul Wold
2011-11-29 23:00 ` [PATCH 11/26] xwininfo: Update to 1.1.2 Saul Wold
2011-11-29 23:00 ` [PATCH 12/26] xf86-input-mouse: Update to 1.7.1 Saul Wold
2011-11-29 23:00 ` [PATCH 13/26] xf86-input-synaptics: Update to 1.5.0 Saul Wold
2011-11-29 23:00 ` [PATCH 14/26] xf86-video-intel: Update to 2.17.0 Saul Wold
2011-11-29 23:00 ` [PATCH 15/26] xserver-xorg*: Update to 1.11.2 Saul Wold
2011-11-29 23:07 ` Martin Jansa
2011-11-29 23:00 ` [PATCH 16/26] lame: Update to 3.99.3 Saul Wold
2011-11-29 23:00 ` [PATCH 17/26] gdbm: Update to 1.10 Saul Wold
2011-11-30 19:00 ` Koen Kooi
2011-11-29 23:00 ` [PATCH 18/26] libtasn1: Update to 2.11 Saul Wold
2011-11-29 23:00 ` [PATCH 19/26] gnutls: Update to 2.12.14 Saul Wold
2011-11-29 23:00 ` [PATCH 20/26] libiconv: Update to 1.14 Saul Wold
2011-11-29 23:08 ` Martin Jansa
2011-11-30 0:07 ` Saul Wold
2011-11-30 0:19 ` Joshua Lock [this message]
2011-11-30 7:29 ` Koen Kooi
2011-11-29 23:00 ` [PATCH 21/26] coreutils: build and install hostname Saul Wold
2011-11-29 23:00 ` [PATCH 22/26] ocf-linux: Add ocf-linux to support openssl 1.0 Saul Wold
2011-11-29 23:00 ` [PATCH 23/26] openssl-0.9.8: move parallel-make fix to 0.9.8 Saul Wold
2011-11-29 23:00 ` [PATCH 24/26] openssl: Add openssl 1.0 Saul Wold
2011-11-29 23:00 ` [PATCH 25/26] PR Bump for OpenSSL 1.0 Saul Wold
2011-11-29 23:00 ` [PATCH 26/26] Distro Tracking: Update Ownership and Update Dates Saul Wold
2011-11-30 15:06 ` [PATCH 00/26] Various Package Updates Richard Purdie
2011-11-30 15:09 ` Koen Kooi
2011-11-30 23:12 ` Richard Purdie
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=4ED5769C.2070905@linux.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@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