From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: ncurses-5.7 patch files are missing
Date: Mon, 11 Apr 2011 13:21:17 -0700 [thread overview]
Message-ID: <4DA362BD.3020703@mentor.com> (raw)
In-Reply-To: <131E5DFBE7373E4C8D813795A6AA7F080340D391AE@dlee06.ent.ti.com>
On 04/11/2011 01:17 PM, Maupin, Chase wrote:
>> -----Original Message-----
>> From: openembedded-devel-bounces@lists.openembedded.org
>> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
>> Henning Heinold
>> Sent: Monday, April 11, 2011 3:12 PM
>> To: openembedded-devel@lists.openembedded.org
>> Subject: Re: [oe] ncurses-5.7 patch files are missing
>>
>> On Mon, Apr 11, 2011 at 03:07:35PM -0500, Maupin, Chase wrote:
>>> All,
>>>
>>> Has anyone else noticed that the patch files referred to in the
>> ncurses_5.7 recipe are missing from the ftp site? The patch files are:
>>>
>>> ncurses-5.7-20110108-patch.sh.bz2
>>> ncurses-5.7-20110115.patch.gz
>>>
>>> Does anyone have these mirrored or can they be uploaded to a mirror like
>> the Angstrom mirror?
>>>
>>>
>>> Sincerely,
>>> Chase Maupin
>>
>> Yes serval people reported that now, I have no acess to upload them. I
>> guess koen will do it when he returns
>> from elc.
>
> Henning,
>
> Thanks. I didn't notice the reports on the mailing list. I did however notice that Tom Rini is adding ncurses version 5.9 to oe-core. I wonder if maybe this should be ported over to the OE mainline or just stick with 5.7+patches for now until everything is moved to oe-core. Anyone else have thoughts on this?
It's already done (I got it in here first).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-04-11 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 20:07 ncurses-5.7 patch files are missing Maupin, Chase
2011-04-11 20:12 ` Henning Heinold
2011-04-11 20:17 ` Maupin, Chase
2011-04-11 20:21 ` Tom Rini [this message]
2011-04-11 20:25 ` Maupin, Chase
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=4DA362BD.3020703@mentor.com \
--to=tom_rini@mentor.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 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.