[GSoC - Tracing] Status

[Vidushi Vashishth]

Hi!

>in case you receive comments for your patches the highest priority should
be to fix the problems with the patches and send the next revision of the
patch to the list, e.g. fixing trivial things like the line ?>length should
be done in a couple of minutes. If you think a comment is invalid or makes
no sense, then please say this also. The patch review process should be as
fast as possible.

I wasn't finished with the documentation and I intended to incorporate the
line length change in the next patch. I got caught up with the babeltrace
conversion hence did not work on the documentation patches. I am sorry you
feel unhappy about the visibility of my work. I will follow your
instructions more carefully. I will upload example codes to my github
repository and notify you.

>I need to know which tools I have to installon top of the standard RTEMS
tools on a normal Linux machine.

Babeltrace is the only tool you need to install for now. The instructions
to install it are mentioned in : http://diamon.org/babeltrace/
I will add these details to the github repository too. I will make the
necessary changes in the user manual as well.

On Tue, Jun 12, 2018 at 5:34 PM, Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello Vidushi,
>
> in case you receive comments for your patches the highest priority should
> be to fix the problems with the patches and send the next revision of the
> patch to the list, e.g. fixing trivial things like the line length should
> be done in a couple of minutes. If you think a comment is invalid or makes
> no sense, then please say this also. The patch review process should be as
> fast as possible.
>
> You posted the "[PATCH v2 2/2] Adding trace documentation" on 10th June
> and got a comment from Gedare on the same day. You acknowledged it on the
> same day and now two days later there is still no next revision of the
> patch.
>
> I am not happy with the visibility of your work. If you work on examples
> then please find a repository (the examples should be a part of RTEMS at
> some point in time) for this stuff which I can clone and try out.
>
> In order to try it out. I need to know which tools I have to installon top
> of the standard RTEMS tools on a normal Linux machine. This information
> should be available in the user manual. I don't need detailed installation
> steps. Just an overview, maybe with links to the external project
> documentation. From my point of view the installation section should be in
> one place and not scattered throughout several sections.
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> <https://maps.google.com/?q=Dornierstr.+4,+D-82178+Puchheim,+Germany&entry=gmail&source=g>
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180612/2381d295/attachment-0002.html>