From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] boost-1.33.1: Corrected GNU_HASH error.
Date: Thu, 5 Nov 2009 10:17:17 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911051014270.7161@localhost> (raw)
In-Reply-To: <4AF2EAF3.5020808@cs.put.poznan.pl>
On Thu, 5 Nov 2009, Przemyslaw Wesolek wrote:
> Henning Heinold wrote:
> > thanks for the patch, but I wonder who is using this older
> > version. Mainly 1.3.36 is used.
>
> Did you mean 1.36?
>
> I agree, the older versions look like unmaintained for a long time.
if you go to boost's home page, they don't even *list* versions
earlier than 1.36:
http://www.boost.org/users/news/
that's generally a good indication that it's time to start
deprecating. and there's already a beta version of 1.41.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2009-11-12 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 13:24 [PATCH] boost-1.33.1: Corrected GNU_HASH error Przemyslaw Wesolek
2009-11-05 13:40 ` Holger Hans Peter Freyther
2009-11-05 15:00 ` [PATCH] boost-1.33.1: Corrected GNU_HASH QA error Przemyslaw Wesolek
2009-11-05 15:12 ` Przemyslaw Wesolek
2009-11-08 22:37 ` Przemyslaw Wesolek
2009-11-09 18:00 ` Leon Woestenberg
2009-11-05 15:04 ` [PATCH] boost-1.33.1: Corrected GNU_HASH error Przemyslaw Wesolek
2009-11-05 14:06 ` Henning Heinold
2009-11-05 15:10 ` Przemyslaw Wesolek
2009-11-05 15:17 ` Robert P. J. Day [this message]
2009-11-12 10:05 ` Przemyslaw Wesolek
2009-11-12 18:53 ` Philip Balister
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=alpine.LFD.2.00.0911051014270.7161@localhost \
--to=rpjday@crashcourse.ca \
--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.