On 15/8/19 5:33 pm, Sebastian Huber wrote:>
> I don't think it is worth to add this switch.
OK.
> I will work on this program in August and September.
>
Thank you.
I have no other specific issues with the code.
Chris
___
devel mailing list
- Am 15. Aug 2019 um 8:26 schrieb Chris Johns chr...@rtems.org:
> On 15/8/19 4:05 pm, Sebastian Huber wrote:
>> - Am 15. Aug 2019 um 2:09 schrieb Chris Johns chr...@rtems.org:
>>
>>> On 14/8/19 3:19 pm, Sebastian Huber wrote:
On 14/08/2019 03:57, Chris Johns wrote:
> On 13/8/19
On 15/8/19 4:05 pm, Sebastian Huber wrote:
> - Am 15. Aug 2019 um 2:09 schrieb Chris Johns chr...@rtems.org:
>
>> On 14/8/19 3:19 pm, Sebastian Huber wrote:
>>> On 14/08/2019 03:57, Chris Johns wrote:
On 13/8/19 3:10 pm, Sebastian Huber wrote:
> sorry for the rush,
Sorry
- Am 15. Aug 2019 um 2:09 schrieb Chris Johns chr...@rtems.org:
> On 14/8/19 3:19 pm, Sebastian Huber wrote:
>> On 14/08/2019 03:57, Chris Johns wrote:
>>> On 13/8/19 3:10 pm, Sebastian Huber wrote:
sorry for the rush,
>>>
>>> Sorry for the delay, I have a client demo this week I am
On 14/8/19 3:19 pm, Sebastian Huber wrote:
> On 14/08/2019 03:57, Chris Johns wrote:
>> On 13/8/19 3:10 pm, Sebastian Huber wrote:
>>> sorry for the rush,
>>
>> Sorry for the delay, I have a client demo this week I am helping with.
>>
>>> but what do you think of this patch?
>>
>> Why not C++? The
On 14/08/2019 03:57, Chris Johns wrote:
On 13/8/19 3:10 pm, Sebastian Huber wrote:
sorry for the rush,
Sorry for the delay, I have a client demo this week I am helping with.
but what do you think of this patch?
Why not C++? The rtems-tools repo has strong support for C++ and it brings a
On 13/8/19 3:10 pm, Sebastian Huber wrote:
> sorry for the rush,
Sorry for the delay, I have a client demo this week I am helping with.
> but what do you think of this patch?
Why not C++? The rtems-tools repo has strong support for C++ and it brings a
range of benefits, for example no need to
Hello Chris,
>
> sorry for the rush, but what do you think of this patch? I would like to
> integrate the tracing work of the GSoC project and this patch is a
> blocking point.
>
Please review the patches. This need to be integrated in master branch
before 19th August (GSoC ends). I have to
Hello Chris,
sorry for the rush, but what do you think of this patch? I would like to
integrate the tracing work of the GSoC project and this patch is a
blocking point.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Update #3665.
---
trace/record/record-client.c | 448 ++
trace/record/record-main.c| 339 +++
trace/record/record-text.c| 1071 +
trace/record/rtems/recordclient.h | 139 +
trace/record/rtems/recorddata.h | 1204
On 31/1/19 5:36 pm, Sebastian Huber wrote:
> On 30/01/2019 22:11, Chris Johns wrote:
>> On 30/1/19 9:31 pm, Sebastian Huber wrote:
>>> Update #3665.
>>> ---
>>> misc/record/record-client.c | 448 ++
>> What about placing this in:
>>
>> trace/record-client.c
>>
>> ?
>>
>> For
On 30/01/2019 22:11, Chris Johns wrote:
On 30/1/19 9:31 pm, Sebastian Huber wrote:
Update #3665.
---
misc/record/record-client.c | 448 ++
What about placing this in:
trace/record-client.c
?
For important parts of the tools, for example linkers and tester, there is a
On 30/1/19 9:31 pm, Sebastian Huber wrote:
> Update #3665.
> ---
> misc/record/record-client.c | 448 ++
What about placing this in:
trace/record-client.c
?
For important parts of the tools, for example linkers and tester, there is a
separate directory. I am sure there will
Update #3665.
---
misc/record/record-client.c | 448 ++
misc/record/record-main.c| 335 +++
misc/record/record-text.c| 1071 +
misc/record/rtems/recordclient.h | 139 +
misc/record/rtems/recorddata.h | 1202
14 matches
Mail list logo
