[prev in list] [next in list] [prev in thread] [next in thread] 

List:       orocos-dev
Subject:    [Orocos-Dev] [Bug 708] Orocos does not support real time logging
From:       kiwi.net () mac ! com (Stephen Roderick)
Date:       2009-11-28 20:13:45
Message-ID: 105FFECC-BF8E-48CD-80C5-2AA8C9DEC6B6 () mac ! com
[Download RAW message or body]

On Nov 13, 2009, at 17:36 , Peter Soetens wrote:

> On Fri, Nov 13, 2009 at 14:00, Stephen Roderick <kiwi.net at mac.com> wrote:
> > On Nov 13, 2009, at 05:10 , Peter Soetens wrote:
> > 
> > > On Wed, Nov 11, 2009 at 22:58, Stephen Roderick <kiwi.net at mac.com> wrote:
> > > > On Nov 11, 2009, at 15:28 , S Roderick wrote:
> > > > 
> > > > > On Nov 11, 2009, at 14:02 , Stephen Roderick wrote:
> > > > > 
> > > > > > On Nov 10, 2009, at 15:07 , Peter Soetens wrote:
> > > > > > 
> > > > > > > On Tue, Nov 10, 2009 at 20:16, S Roderick <kiwi.net at mac.com> wrote:
> > > > > > > > 
> > > > > > > > On Nov 10, 2009, at 09:38 , S Roderick wrote:
> > > > > > > > 
> > > > > > > > > On Nov 10, 2009, at 09:28 , Peter Soetens wrote:
> > > > > > > > > 
> > > > > > > > > > https://www.fmtc.be/bugzilla/orocos/show_bug.cgi?id=708

<snip>

> > 
> > Personally, I'm not worried about releases. I plan to use these on a 1.x branch \
> > in my own git repo, but I will open a ticket so that others can follow along if \
> > they want to. 
> > Thanks for your help with this.
> 
> Now that you're using git, why don't you push your 1.x branch to
> github (name it 'for-peter'), then I can pull it in. It's gonna be
> less time for you instead of  creating bug reports and it's less time
> for me to review and merge the patches in.

I've done this for bug 733, the integration of TLSF into RTT, plus my patches. I sent \
you a pull request. First time at this, so please let me know if it is working for \
you. If it works, then I will also do this for OCL and the other real-time logging \
related patches.

Also, I'm curious how people have setup their repo's if using github. Particularly \
when it comes to forking from an existing github repo. I've forked snrkiwi/orocos-rtt \
from psoetens/orocos-rtt. I then have a copy of that public repo on my machine. Am I \
better off then to clone this public repo to a private repo on my own machine, and \
work on the private repo, pushing to public and then to github periodically? Or am I \
better off trying to also link the public repo back to a completely separate private \
repo, which is separately tracking your github public repo? Ugh, kinda confusing ... \
any suggestions, anyone?

Lastly, if at all possible I am hoping to get all these patches into github for you \
this week. Would love to leave you plenty of patches for review, before I dissappear \
on a god-awful long flight home to some Kiwi sunshine for a month. :-)

Cheers
Stephen


[prev in list] [next in list] [prev in thread] [next in thread]