From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: tsc <tsc@lists.openembedded.org>,
openembedded-devel@lists.openembedded.org
Subject: Re: OpenEmbedded TSC Meeting 17-Nov-2011
Date: Mon, 28 Nov 2011 10:11:20 +0000 [thread overview]
Message-ID: <1322475081.26081.79.camel@phil-desktop> (raw)
In-Reply-To: <CA+YB3rZzq1zu9UCqZo4H4OypRdPyRObzahLjejp-qxXbzum+aw@mail.gmail.com>
On Wed, 2011-11-23 at 10:18 -0800, Jeff Osier-Mixon wrote:
> berlios disappearing
Just as an observation, this business of "berlios going away at the end
of the year" seems to crop up in the TSC minutes fairly often but
appears to be incorrect (or at least outdated). According to the
berlios website, it doesn't appear that there is an imminent threat of
it disappearing.
That's not to say that I think moving bitbake off berlios and onto
oe.org wouldn't be a good thing, but perhaps it isn't as urgent as all
that.
p.
next prev parent reply other threads:[~2011-11-28 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 18:18 OpenEmbedded TSC Meeting 17-Nov-2011 Jeff Osier-Mixon
2011-11-28 10:11 ` Phil Blundell [this message]
2011-11-28 10:39 ` Richard Purdie
2011-11-28 10:40 ` Koen Kooi
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=1322475081.26081.79.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=tsc@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