[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: "Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>
- Date: Tue, 19 Feb 2008 09:15:47 -0800
- Delivered-to: email@example.com
- Thread-index: AchysSqGc6XLfTPCRKmcckQJJt7GpQAXwU7AAAGG2uAAALbBoAAAbC2w
- Thread-topic: [cdt-dev] M5 Broken
I tend to agree. Although I'm not sure our releng system is
robust enough to quickly throw this together. Vivian do you think we could do
this quickly, i.e., create a branch and munge the scripts to build off of
I have committed a bunch of things since then. All of that
passes our test-suites and the indexer works for my test
However, I'd go with the defensive approach
of creating a branch,
We need to discuss. There were a lot of changes since M5
and I'm not sure how sane they are. We may just want to create a branch for
the fix and build from there. What are people thoughts on that? Especially
those who committed stuff since the M5 build.
Will the respin contain the latest HEAD version, or just
the current M5 plus the fixed references?
Hey gang, a
couple of points.
First, make sure
you build against the Eclipse Platform Runtime once in a while. This is the
minimum Eclipse package that we support and we shouldn't be depending on
things outside it, at least without approval from the
That brings up
the next point. M5 is broken because of this and we need to do a respin
since it also breaks the Ganymede C/C++ IDE Package. The following bug is
tracking the issue.
We'll kick off
the respin once it's fixed.