From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] ncurses: Update to 5.9
Date: Wed, 06 Apr 2011 11:38:34 -0700 [thread overview]
Message-ID: <1302115114.22904.77.camel@rex> (raw)
In-Reply-To: <BANLkTi=RTLB21JAz4N2B2kPWu6H3uTHn1w@mail.gmail.com>
On Tue, 2011-04-05 at 23:18 -0700, Khem Raj wrote:
> On Tue, Apr 5, 2011 at 5:38 PM, Tom Rini <tom_rini@mentor.com> wrote:
> > The previous 5.7 release was relatively close to 5.8 due to it bringing
> > in a patch to sync with upstream work-in-progress. We skip over the
> > 5.8 release and move to 5.9.
>
>
> there already are patches for 5.9 available too
> ftp://invisible-island.net/ncurses/5.9/ncurses-5.9.patch.gz
Can someone summarise what the benefits of these patches are? I'm
trying to figure out whether we lose anything due to this upgrade or
not...
Cheers,
Richard
next prev parent reply other threads:[~2011-04-06 19:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 0:37 [PATCH 0/1] Update ncurses Tom Rini
2011-04-06 0:38 ` [PATCH 1/1] ncurses: Update to 5.9 Tom Rini
2011-04-06 6:18 ` Khem Raj
2011-04-06 14:30 ` Tom Rini
2011-04-06 17:05 ` Khem Raj
2011-04-06 17:10 ` Tom Rini
2011-04-06 17:26 ` Khem Raj
2011-04-06 17:35 ` Tom Rini
2011-04-06 18:27 ` Khem Raj
2011-04-06 18:29 ` Tom Rini
2011-04-06 18:32 ` Khem Raj
2011-04-06 18:48 ` Tom Rini
2011-04-06 20:56 ` Khem Raj
2011-04-06 21:16 ` Richard Purdie
2011-04-07 0:35 ` Tom Rini
2011-04-06 18:38 ` Richard Purdie [this message]
2011-04-06 19:20 ` Tom Rini
2011-04-06 20:54 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2011-04-07 0:50 [PATCH 0/1] v2: Update ncurses Tom Rini
2011-04-07 0:50 ` [PATCH 1/1] ncurses: Update to 5.9 Tom Rini
2011-04-08 13:19 ` 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=1302115114.22904.77.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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