From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Boost
Date: Sat, 03 Jan 2009 19:18:54 -0500 [thread overview]
Message-ID: <4960006E.6090706@balister.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
Last year we had some discussion of creating separate boost packages
based on different versions (since boost has API changes between revs).
I would like to talk about this again, since I am running into this
issue again.
Thoughts?
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next reply other threads:[~2009-01-04 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 0:18 Philip Balister [this message]
2009-01-06 8:38 ` Boost Robert Schuster
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=4960006E.6090706@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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