ocl rttlua tlsf patch reverted?
| Submitted by dustingooding on Thu, 2012-11-29 19:39 |
I submitted a patch file for OCL to this list some time ago. Specifically, it was to enable real-time memory (TLSF) via rttlua, along with some example code. In the toolchain-2.5 git log, I see that patch was reverted on Sept 27. Why?
We still need rttlua TLSF functionality. Can the patch be reapplied? I'd like it to be included in the toolchain-2.5 debs, if it's not too late.
--
Dustin Gooding
NASA/JSC Robotics
| Attachment | Size |
|---|---|
| ocl-rttlua-tlsf.patch | 12.72 KB |
ocl rttlua tlsf patch reverted?
On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
<dustin [dot] r [dot] gooding [..] ...> wrote:
> I submitted a patch file for OCL to this list some time ago. Specifically,
> it was to enable real-time memory (TLSF) via rttlua, along with some example
> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
> 27. Why?
>
> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
> like it to be included in the toolchain-2.5 debs, if it's not too late.
I do remember that I had to revert the modifications to manifest.xml,
because they were pushed accidentally to gitorious. Maybe I was
unsure about the status of these other commits, ie, if they were
working fine. They did remain on master.
I pushed the two commits back to toolchain-2.5. The ROS deb build
system is quite unstable nowadays, so I don't know when there will be
a window to push them to the debs. For fuerte & groovy, these are
toolchain-2.6 and will contain these patches
Peter
ocl rttlua tlsf patch reverted?
On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
> On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
> <dustin [dot] r [dot] gooding [..] ...> wrote:
>> I submitted a patch file for OCL to this list some time ago. Specifically,
>> it was to enable real-time memory (TLSF) via rttlua, along with some example
>> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
>> 27. Why?
>>
>> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
>> like it to be included in the toolchain-2.5 debs, if it's not too late.
>
> I do remember that I had to revert the modifications to manifest.xml,
> because they were pushed accidentally to gitorious. Maybe I was
> unsure about the status of these other commits, ie, if they were
> working fine. They did remain on master.
>
> I pushed the two commits back to toolchain-2.5. The ROS deb build
> system is quite unstable nowadays, so I don't know when there will be
> a window to push them to the debs. For fuerte & groovy, these are
> toolchain-2.6 and will contain these patches
>
> Peter
Thanks. For what it's worth, I can't clone the OCL repo:
$ git clone https://git.gitorious.org/orocos-toolchain/ocl.git
Cloning into 'ocl'...
error: Unable to get pack index https://git.gitorious.org/orocos-toolchain/ocl.git/objects/pack/pack-983...
error: Unable to find 8faecd55ec6466039fca989ae71da46cd1def615 under https://git.gitorious.org/orocos-toolchain/ocl.git
Cannot obtain needed object 8faecd55ec6466039fca989ae71da46cd1def615
while processing commit fd0f873ca3c0112cf2778f7983846a1c93d64d5b.
error: Fetch failed.
-dustin
ocl rttlua tlsf patch reverted?
Hi Dustin,
On Thu, Nov 29, 2012 at 11:36 PM, Gooding, Dustin R. (JSC-ER411)
<dustin [dot] r [dot] gooding [..] ...> wrote:
>
> On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
>
> > On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
> > <dustin [dot] r [dot] gooding [..] ...> wrote:
> >> I submitted a patch file for OCL to this list some time ago. Specifically,
> >> it was to enable real-time memory (TLSF) via rttlua, along with some example
> >> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
> >> 27. Why?
> >>
> >> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
> >> like it to be included in the toolchain-2.5 debs, if it's not too late.
> >
> > I do remember that I had to revert the modifications to manifest.xml,
> > because they were pushed accidentally to gitorious. Maybe I was
> > unsure about the status of these other commits, ie, if they were
> > working fine. They did remain on master.
> >
> > I pushed the two commits back to toolchain-2.5. The ROS deb build
> > system is quite unstable nowadays, so I don't know when there will be
> > a window to push them to the debs. For fuerte & groovy, these are
> > toolchain-2.6 and will contain these patches
> >
> > Peter
>
> Thanks. For what it's worth, I can't clone the OCL repo:
>
> $ git clone https://git.gitorious.org/orocos-toolchain/ocl.git
> Cloning into 'ocl'...
> error: Unable to get pack index https://git.gitorious.org/orocos-toolchain/ocl.git/objects/pack/pack-983...
>
> error: Unable to find 8faecd55ec6466039fca989ae71da46cd1def615 under https://git.gitorious.org/orocos-toolchain/ocl.git
> Cannot obtain needed object 8faecd55ec6466039fca989ae71da46cd1def615
> while processing commit fd0f873ca3c0112cf2778f7983846a1c93d64d5b.
> error: Fetch failed.
I can reproduce this, can you retry with the git protocol:
git clone git://git.gitorious.org/orocos-toolchain/ocl.git
This worked for me without a flaw. Maybe the https protocol is still
somewhat broken after gitorious' server upgrade of Tuesday.
Ruben
> -dustin
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
ocl rttlua tlsf patch reverted?
On Nov 30, 2012, at 3:14 AM, Ruben Smits wrote:
> Hi Dustin,
>
> On Thu, Nov 29, 2012 at 11:36 PM, Gooding, Dustin R. (JSC-ER411)
> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>
>> On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
>>
>>> On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
>>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>>> I submitted a patch file for OCL to this list some time ago. Specifically,
>>>> it was to enable real-time memory (TLSF) via rttlua, along with some example
>>>> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
>>>> 27. Why?
>>>>
>>>> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
>>>> like it to be included in the toolchain-2.5 debs, if it's not too late.
>>>
>>> I do remember that I had to revert the modifications to manifest.xml,
>>> because they were pushed accidentally to gitorious. Maybe I was
>>> unsure about the status of these other commits, ie, if they were
>>> working fine. They did remain on master.
>>>
>>> I pushed the two commits back to toolchain-2.5. The ROS deb build
>>> system is quite unstable nowadays, so I don't know when there will be
>>> a window to push them to the debs. For fuerte & groovy, these are
>>> toolchain-2.6 and will contain these patches
>>>
>>> Peter
>>
>> Thanks. For what it's worth, I can't clone the OCL repo:
>>
>> $ git clone https://git.gitorious.org/orocos-toolchain/ocl.git
>> Cloning into 'ocl'...
>> error: Unable to get pack index https://git.gitorious.org/orocos-toolchain/ocl.git/objects/pack/pack-983...
>>
>> error: Unable to find 8faecd55ec6466039fca989ae71da46cd1def615 under https://git.gitorious.org/orocos-toolchain/ocl.git
>> Cannot obtain needed object 8faecd55ec6466039fca989ae71da46cd1def615
>> while processing commit fd0f873ca3c0112cf2778f7983846a1c93d64d5b.
>> error: Fetch failed.
>
> I can reproduce this, can you retry with the git protocol:
>
> git clone git://git.gitorious.org/orocos-toolchain/ocl.git
>
> This worked for me without a flaw. Maybe the https protocol is still
> somewhat broken after gitorious' server upgrade of Tuesday.
>
> Ruben
Unfortunately, our corporate firewall (stupidly) blocks the git protocol, so I have to use https whenever I'm on-site. I ended up using the GitHub mirror.
-dustin
ocl rttlua tlsf patch reverted?
On Nov 30, 2012, at 7:50 AM, Gooding, Dustin R. (JSC-ER411) wrote:
> On Nov 30, 2012, at 3:14 AM, Ruben Smits wrote:
>
>> Hi Dustin,
>>
>> On Thu, Nov 29, 2012 at 11:36 PM, Gooding, Dustin R. (JSC-ER411)
>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>>
>>> On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
>>>
>>>> On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
>>>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>>>> I submitted a patch file for OCL to this list some time ago. Specifically,
>>>>> it was to enable real-time memory (TLSF) via rttlua, along with some example
>>>>> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
>>>>> 27. Why?
>>>>>
>>>>> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
>>>>> like it to be included in the toolchain-2.5 debs, if it's not too late.
>>>>
>>>> I do remember that I had to revert the modifications to manifest.xml,
>>>> because they were pushed accidentally to gitorious. Maybe I was
>>>> unsure about the status of these other commits, ie, if they were
>>>> working fine. They did remain on master.
>>>>
>>>> I pushed the two commits back to toolchain-2.5. The ROS deb build
>>>> system is quite unstable nowadays, so I don't know when there will be
>>>> a window to push them to the debs. For fuerte & groovy, these are
>>>> toolchain-2.6 and will contain these patches
>>>>
>>>> Peter
>>>
>>> Thanks. For what it's worth, I can't clone the OCL repo:
>>>
>>> $ git clone https://git.gitorious.org/orocos-toolchain/ocl.git
>>> Cloning into 'ocl'...
>>> error: Unable to get pack index https://git.gitorious.org/orocos-toolchain/ocl.git/objects/pack/pack-983...
>>>
>>> error: Unable to find 8faecd55ec6466039fca989ae71da46cd1def615 under https://git.gitorious.org/orocos-toolchain/ocl.git
>>> Cannot obtain needed object 8faecd55ec6466039fca989ae71da46cd1def615
>>> while processing commit fd0f873ca3c0112cf2778f7983846a1c93d64d5b.
>>> error: Fetch failed.
>>
>> I can reproduce this, can you retry with the git protocol:
>>
>> git clone git://git.gitorious.org/orocos-toolchain/ocl.git
>>
>> This worked for me without a flaw. Maybe the https protocol is still
>> somewhat broken after gitorious' server upgrade of Tuesday.
>>
>> Ruben
>
>
> Unfortunately, our corporate firewall (stupidly) blocks the git protocol, so I have to use https whenever I'm on-site. I ended up using the GitHub mirror.
>
> -dustin
ocl rttlua tlsf patch reverted?
On Fri, Nov 30, 2012 at 3:45 PM, Gooding, Dustin R. (JSC-ER411)
<dustin [dot] r [dot] gooding [..] ...> wrote:
> On Nov 30, 2012, at 7:50 AM, Gooding, Dustin R. (JSC-ER411) wrote:
>
>> On Nov 30, 2012, at 3:14 AM, Ruben Smits wrote:
>>
>>> Hi Dustin,
>>>
>>> On Thu, Nov 29, 2012 at 11:36 PM, Gooding, Dustin R. (JSC-ER411)
>>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>>>
>>>> On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
>>>>
>>>>> On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
>>>>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>>>>> I submitted a patch file for OCL to this list some time ago. Specifically,
>>>>>> it was to enable real-time memory (TLSF) via rttlua, along with some example
>>>>>> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
>>>>>> 27. Why?
>>>>>>
>>>>>> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
>>>>>> like it to be included in the toolchain-2.5 debs, if it's not too late.
>>>>>
>>>>> I do remember that I had to revert the modifications to manifest.xml,
>>>>> because they were pushed accidentally to gitorious. Maybe I was
>>>>> unsure about the status of these other commits, ie, if they were
>>>>> working fine. They did remain on master.
>>>>>
>>>>> I pushed the two commits back to toolchain-2.5. The ROS deb build
>>>>> system is quite unstable nowadays, so I don't know when there will be
>>>>> a window to push them to the debs. For fuerte & groovy, these are
>>>>> toolchain-2.6 and will contain these patches
>>>>>
>>>>> Peter
>>>>
>>>> Thanks. For what it's worth, I can't clone the OCL repo:
>>>>
>>>> $ git clone https://git.gitorious.org/orocos-toolchain/ocl.git
>>>> Cloning into 'ocl'...
>>>> error: Unable to get pack index https://git.gitorious.org/orocos-toolchain/ocl.git/objects/pack/pack-983...
>>>>
>>>> error: Unable to find 8faecd55ec6466039fca989ae71da46cd1def615 under https://git.gitorious.org/orocos-toolchain/ocl.git
>>>> Cannot obtain needed object 8faecd55ec6466039fca989ae71da46cd1def615
>>>> while processing commit fd0f873ca3c0112cf2778f7983846a1c93d64d5b.
>>>> error: Fetch failed.
>>>
>>> I can reproduce this, can you retry with the git protocol:
>>>
>>> git clone git://git.gitorious.org/orocos-toolchain/ocl.git
>>>
>>> This worked for me without a flaw. Maybe the https protocol is still
>>> somewhat broken after gitorious' server upgrade of Tuesday.
>>>
>>> Ruben
>>
>>
>> Unfortunately, our corporate firewall (stupidly) blocks the git protocol, so I have to use https whenever I'm on-site. I ended up using the GitHub mirror.
>>
>> -dustin
>> --
>> Orocos-Users mailing list
>> Orocos-Users [..] ...
>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
> Follow on question:
>
> When I clone --recursive orocos_toolchain, then checkout toolchain-2.5, then do submodule init and update, should the submodules checkout to their respective toolchain-2.5 branches? I would expect that, but that doesn't seem to be the case. Do I need to go through all the submodules and force them to their toolchain-2.5 branches manually?
That's how submodules work. It *is* on the toolchain-2.5 branch, but
git will show the commit hash instead of the branch name. A submodule
is at a certain commit, not a certain branch in git semantics.
Frankly, I just do a 'git submodule foreach git checkout
toolchain-2.5' once in orocos_toolchain and then work on these
branches.
Peter
ocl rttlua tlsf patch reverted?
On Nov 30, 2012, at 8:59 AM, Peter Soetens wrote:
> On Fri, Nov 30, 2012 at 3:45 PM, Gooding, Dustin R. (JSC-ER411)
> <dustin [dot] r [dot] gooding [..] ...> wrote:
>> On Nov 30, 2012, at 7:50 AM, Gooding, Dustin R. (JSC-ER411) wrote:
>>
>>> On Nov 30, 2012, at 3:14 AM, Ruben Smits wrote:
>>>
>>>> Hi Dustin,
>>>>
>>>> On Thu, Nov 29, 2012 at 11:36 PM, Gooding, Dustin R. (JSC-ER411)
>>>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>>>>
>>>>> On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
>>>>>
>>>>>> On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
>>>>>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>>>>>> I submitted a patch file for OCL to this list some time ago. Specifically,
>>>>>>> it was to enable real-time memory (TLSF) via rttlua, along with some example
>>>>>>> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
>>>>>>> 27. Why?
>>>>>>>
>>>>>>> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
>>>>>>> like it to be included in the toolchain-2.5 debs, if it's not too late.
>>>>>>
>>>>>> I do remember that I had to revert the modifications to manifest.xml,
>>>>>> because they were pushed accidentally to gitorious. Maybe I was
>>>>>> unsure about the status of these other commits, ie, if they were
>>>>>> working fine. They did remain on master.
>>>>>>
>>>>>> I pushed the two commits back to toolchain-2.5. The ROS deb build
>>>>>> system is quite unstable nowadays, so I don't know when there will be
>>>>>> a window to push them to the debs. For fuerte & groovy, these are
>>>>>> toolchain-2.6 and will contain these patches
>>>>>>
>>>>>> Peter
>>>>>
>>>>> Thanks. For what it's worth, I can't clone the OCL repo:
>>>>>
>>>>> $ git clone https://git.gitorious.org/orocos-toolchain/ocl.git
>>>>> Cloning into 'ocl'...
>>>>> error: Unable to get pack index https://git.gitorious.org/orocos-toolchain/ocl.git/objects/pack/pack-983...
>>>>>
>>>>> error: Unable to find 8faecd55ec6466039fca989ae71da46cd1def615 under https://git.gitorious.org/orocos-toolchain/ocl.git
>>>>> Cannot obtain needed object 8faecd55ec6466039fca989ae71da46cd1def615
>>>>> while processing commit fd0f873ca3c0112cf2778f7983846a1c93d64d5b.
>>>>> error: Fetch failed.
>>>>
>>>> I can reproduce this, can you retry with the git protocol:
>>>>
>>>> git clone git://git.gitorious.org/orocos-toolchain/ocl.git
>>>>
>>>> This worked for me without a flaw. Maybe the https protocol is still
>>>> somewhat broken after gitorious' server upgrade of Tuesday.
>>>>
>>>> Ruben
>>>
>>>
>>> Unfortunately, our corporate firewall (stupidly) blocks the git protocol, so I have to use https whenever I'm on-site. I ended up using the GitHub mirror.
>>>
>>> -dustin
>>> --
>>> Orocos-Users mailing list
>>> Orocos-Users [..] ...
>>> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>>
>> Follow on question:
>>
>> When I clone --recursive orocos_toolchain, then checkout toolchain-2.5, then do submodule init and update, should the submodules checkout to their respective toolchain-2.5 branches? I would expect that, but that doesn't seem to be the case. Do I need to go through all the submodules and force them to their toolchain-2.5 branches manually?
>
> That's how submodules work. It *is* on the toolchain-2.5 branch, but
> git will show the commit hash instead of the branch name. A submodule
> is at a certain commit, not a certain branch in git semantics.
>
> Frankly, I just do a 'git submodule foreach git checkout
> toolchain-2.5' once in orocos_toolchain and then work on these
> branches.
>
> Peter
But that's just it. I did an update and checked the git log for ocl, then manually checked out ocl's toolchain-2.5 and checked the log, and the logs were different… Maybe I'm doing something else wrong… The 'foreach' command is probably least prone to failure, though.
-dustin
ocl rttlua tlsf patch reverted?
On Fri, Nov 30, 2012 at 4:10 PM, Gooding, Dustin R. (JSC-ER411)
<dustin [dot] r [dot] gooding [..] ...> wrote:
>>>
>>> Follow on question:
>>>
>>> When I clone --recursive orocos_toolchain, then checkout toolchain-2.5, then do submodule init and update, should the submodules checkout to their respective toolchain-2.5 branches? I would expect that, but that doesn't seem to be the case. Do I need to go through all the submodules and force them to their toolchain-2.5 branches manually?
>>
>> That's how submodules work. It *is* on the toolchain-2.5 branch, but
>> git will show the commit hash instead of the branch name. A submodule
>> is at a certain commit, not a certain branch in git semantics.
>>
>> Frankly, I just do a 'git submodule foreach git checkout
>> toolchain-2.5' once in orocos_toolchain and then work on these
>> branches.
>>
>> Peter
>
> But that's just it. I did an update and checked the git log for ocl, then manually checked out ocl's toolchain-2.5 and checked the log, and the logs were different… Maybe I'm doing something else wrong… The 'foreach' command is probably least prone to failure, though.
We don't update orocos_toolchain each time we update a submodule, so
often, orocos_toolchain is a few patches behind. It's not an automatic
'tracking', we have to do it manually (or using a hudson/jenkins job).
Peter
ocl rttlua tlsf patch reverted?
On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
> On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
> <dustin [dot] r [dot] gooding [..] ...> wrote:
>> I submitted a patch file for OCL to this list some time ago. Specifically,
>> it was to enable real-time memory (TLSF) via rttlua, along with some example
>> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
>> 27. Why?
>>
>> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
>> like it to be included in the toolchain-2.5 debs, if it's not too late.
>
> I do remember that I had to revert the modifications to manifest.xml,
> because they were pushed accidentally to gitorious. Maybe I was
> unsure about the status of these other commits, ie, if they were
> working fine. They did remain on master.
>
> I pushed the two commits back to toolchain-2.5. The ROS deb build
> system is quite unstable nowadays, so I don't know when there will be
> a window to push them to the debs. For fuerte & groovy, these are
> toolchain-2.6 and will contain these patches
>
> Peter
We have quite a few developers here using the patch I provided. At least in our use-cases, it works fine. In fact, our code doesn't work without it. ;)
Do you advise an upgrade to toolchain-2.6? Will there be a named branch for 2.6 (akin to 2.5), or is that just "master"?
-dustin
ocl rttlua tlsf patch reverted?
On Thu, Nov 29, 2012 at 9:39 PM, Gooding, Dustin R. (JSC-ER411)
<dustin [dot] r [dot] gooding [..] ...> wrote:
> On Nov 29, 2012, at 2:35 PM, Peter Soetens wrote:
>
>> On Thu, Nov 29, 2012 at 8:39 PM, Gooding, Dustin R. (JSC-ER411)
>> <dustin [dot] r [dot] gooding [..] ...> wrote:
>>> I submitted a patch file for OCL to this list some time ago. Specifically,
>>> it was to enable real-time memory (TLSF) via rttlua, along with some example
>>> code. In the toolchain-2.5 git log, I see that patch was reverted on Sept
>>> 27. Why?
>>>
>>> We still need rttlua TLSF functionality. Can the patch be reapplied? I'd
>>> like it to be included in the toolchain-2.5 debs, if it's not too late.
>>
>> I do remember that I had to revert the modifications to manifest.xml,
>> because they were pushed accidentally to gitorious. Maybe I was
>> unsure about the status of these other commits, ie, if they were
>> working fine. They did remain on master.
>>
>> I pushed the two commits back to toolchain-2.5. The ROS deb build
>> system is quite unstable nowadays, so I don't know when there will be
>> a window to push them to the debs. For fuerte & groovy, these are
>> toolchain-2.6 and will contain these patches
>>
>> Peter
>
> We have quite a few developers here using the patch I provided. At least in our use-cases, it works fine. In fact, our code doesn't work without it. ;)
>
> Do you advise an upgrade to toolchain-2.6? Will there be a named branch for 2.6 (akin to 2.5), or is that just "master"?
Upgrade: yes. Due to typekit stability issues and little-to-none API
changes (except some internals and some new functions added). Quite
some people are running stable applications on master/2.6 right now.
Also note that the reporting improved immensely in 2.6, especially
when reporting to the NetCDF fileformat.
Release: It will be named toolchain-2.6. We're just gaining a bit
confidence on the build farm, the version numbers have bumped already
and the release notes have been written. There are Orocos ROS package
ready for fuerte, but the latest bugfix is somehow stuck in the ROS
deb build farm (they are fixing this right *now*).
I just branched toolchain-2.6 from master and I'm running some release
scripts. We're getting really close now.
Peter