[PATCH] Basic Support for Trace Compass

[Gedare Bloom]

On Fri, Jun 7, 2019 at 12:11 AM Chris Johns <chrisj at rtems.org> wrote:
>
> On 7/6/19 3:51 pm, Sebastian Huber wrote:
> > On 07/06/2019 07:21, Chris Johns wrote:
> >>>> Should we have something working before we make any additions to the user
> >>>> manual?
> >>> It was actually my idea to add this section right now. My experience is that
> >>> documentation which is planned at the end of the project is never written.
> >> Great and I also encourage this happening as well as posting for review but I am
> >> not sure about merging into the main repo until you have some of the other
> >> pieces place. Also I am not suggesting the support needs to be a polished
> >> finished package, it just needs some more time to mature a little.
> >
> > Ok, what should be the modus operandi for this GSoC project? Work with Github
> > forks and occasionally merge patches to upstream?
>
> It depends. Github is one method used in the past and I have even used the
> commit comments it offers. You could host the repos in your personal area and
> add the patches that are reviewed and pending to be merged upstream. It all
> depends on what you and your student are happy to work with.
>

We require that our GSoC Students keep their contributions visible on
their personal GitHub. I recommend that Ravindra stage the work on
personal GitHub, and post here for review by the community. Merge from
personal GitHub to git.rtems.org when sufficiently mature for master.
Work should continue on the personal GitHub, submitting to ML and
merging to master as development proceeds.

Gedare

> > For me it is important to have the current state available somewhere. I don't
> > want to work with content spread throughout e-mails and patches.
>
> I agree.
>
> Chris
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel