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
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
