OCL v1 updates
| Submitted by snrkiwi on Tue, 2011-04-26 00:44 |
Patch for boost v1.46
S
| Attachment | Size |
|---|---|
| 0001-deployment-Cope-with-boost-filesystem-v3-changes.patch | 2.42 KB |
Orocos Real-Time Toolkit
Smarter realtime. Safer threads
Orocos Real-Time ToolkitSmarter realtime. Safer threads
|
|
OCL v1 updates
Patch for boost v1.46
|
OCL v1 updates
On Tue, Apr 26, 2011 at 2:43 AM, S Roderick <kiwi [dot] net [..] ...> wrote:
> Patch for boost v1.46
> S
Thanks for the fix. Note that the git ocl-1.0-svn branch was severely
out of date with respect to the SVN trunk. I'll setup a Hudson job
that automates this synchronising of branches.
Peter
OCL v1 updates
On Apr 26, 2011, at 03:45 , Peter Soetens wrote:
> On Tue, Apr 26, 2011 at 2:43 AM, S Roderick <kiwi [dot] net [..] ...> wrote:
>> Patch for boost v1.46
>> S
>
> Thanks for the fix. Note that the git ocl-1.0-svn branch was severely
> out of date with respect to the SVN trunk. I'll setup a Hudson job
> that automates this synchronising of branches.
>
> Peter
That makes some sense. I was poking around trying to find any recent activity, and the latest commits were 2010-10. I know you'd made changes since then ... so you are planning on keeping your github ocl branch up to date then?
S
Re: OCL v1 updates
> On Tue, Apr 26, 2011 at 2:43 AM, S Roderick <kiwi [dot] net [..] ...> wrote: >> Patch for boost v1.46 >> S > > Thanks for the fix. Note that the git ocl-1.0-svn branch was severely > out of date with respect to the SVN trunk. I'll setup a Hudson job > that automates this synchronising of branches. > > Peter
That makes some sense. I was poking around trying to find any recent activity, and the latest commits were 2010-10. I know you'd made changes since then ... so you are planning on keeping your github ocl branch up to date then? SI think I already sent in a patch for the same thing before, both for rtt and ocl, see: http://www.orocos.org/forum/rtt/rtt-dev/patch-compilation-errors-rtt-230-boost-146
I think Peter applied those, but you missed them because of the lack of synchronisation.
Theo.
Re: OCL v1 updates
> On Tue, Apr 26, 2011 at 2:43 AM, S Roderick <kiwi [dot] net [..] ...> wrote: >> Patch for boost v1.46 >> S > > Thanks for the fix. Note that the git ocl-1.0-svn branch was severely > out of date with respect to the SVN trunk. I'll setup a Hudson job > that automates this synchronising of branches. > > Peter
That makes some sense. I was poking around trying to find any recent activity, and the latest commits were 2010-10. I know you'd made changes since then ... so you are planning on keeping your github ocl branch up to date then? SI think I already sent in a patch for the same thing before, both for rtt and ocl, see: http://www.orocos.org/forum/rtt/rtt-dev/patch-compilation-errors-rtt-230-boost-146
I think Peter applied those, but you missed them because of the lack of synchronisation.
Theo.
Sorry, my bad, this is for v1! Forget about my comment...
Theo.
OCL v1 updates
On Apr 26, 2011, at 06:44 , t [dot] j [dot] a [dot] devries [..] ... wrote:
>
>
>> On Tue, Apr 26, 2011 at 2:43 AM, S Roderick <kiwi [dot] net [..] ...> wrote:
>>> Patch for boost v1.46
>>> S
>>
>> Thanks for the fix. Note that the git ocl-1.0-svn branch was severely
>> out of date with respect to the SVN trunk. I'll setup a Hudson job
>> that automates this synchronising of branches.
>>
>> Peter
>
> That makes some sense. I was poking around trying to find any recent activity, and the latest commits were 2010-10. I know you'd made changes since then ... so you are planning on keeping your github ocl branch up to date then?
> S
>
>
> I think I already sent in a patch for the same thing before, both for rtt and ocl, see:
> http://www.orocos.org/forum/rtt/rtt-dev/patch-compilation-errors-rtt-230...
>
> I think Peter applied those, but you missed them because of the lack of synchronisation.
>
> Theo.
Now that I look at that thread, it rings a bell seeing your patches on the ML. But I did look for boost 1.46 related items the other day, with no luck. I also remember a couple of other bugs I filed a few months back, and couldn't find them either. Are we sure that all the bugs came over with the host or Drupal update we did (I don't remember which it was)? Or might the forum search be broken? Or was it just user error ...
Peter do you remember a bug I filed re unable to use rt_string in state machines? I believe I even sent in a test case for it. I can't find that one.
Different topic - is there a reason we're still doing svn/git sync'ing at all? Seems like extra work. What is the benefit?
S
OCL v1 updates
On Tuesday 26 April 2011 12:56:02 S Roderick wrote:
> On Apr 26, 2011, at 06:44 , t [dot] j [dot] a [dot] devries [..] ... wrote:
> >
> >> On Tue, Apr 26, 2011 at 2:43 AM, S Roderick <kiwi [dot] net [..] ...> wrote:
> >>> Patch for boost v1.46
> >>> S
> >>
> >> Thanks for the fix. Note that the git ocl-1.0-svn branch was severely
> >> out of date with respect to the SVN trunk. I'll setup a Hudson job
> >> that automates this synchronising of branches.
> >>
> >> Peter
> >
> > That makes some sense. I was poking around trying to find any recent
> > activity, and the latest commits were 2010-10. I know you'd made changes
> > since then ... so you are planning on keeping your github ocl branch up
> > to date then? S
> >
> >
> > I think I already sent in a patch for the same thing before, both for rtt
> > and ocl, see:
> > http://www.orocos.org/forum/rtt/rtt-dev/patch-compilation-errors-rtt-230
> > -boost-146
> >
> > I think Peter applied those, but you missed them because of the lack of
> > synchronisation.
> >
> > Theo.
>
> Now that I look at that thread, it rings a bell seeing your patches on the
> ML. But I did look for boost 1.46 related items the other day, with no
> luck. I also remember a couple of other bugs I filed a few months back,
> and couldn't find them either. Are we sure that all the bugs came over
> with the host or Drupal update we did (I don't remember which it was)? Or
> might the forum search be broken? Or was it just user error ...
>
> Peter do you remember a bug I filed re unable to use rt_string in state
> machines? I believe I even sent in a test case for it. I can't find that
> one.
>
> Different topic - is there a reason we're still doing svn/git sync'ing at
> all? Seems like extra work. What is the benefit? S
It is extra work, but 1.x releases are made of the svn branches and I did not
want to complicate things more for existing 1.x users, by also changing the
version control system. It's hard to get a vote about this, because most devs
would vote 'git-only', but I don't think the users are that vocal, and these
would be the ones most hurt.
Peter