On 23/5/19 3:40 pm, Sebastian Huber wrote: > On 23/05/2019 07:35, Chris Johns wrote: >> On 23/5/19 12:25 am, Sebastian Huber wrote: >>> We definitely need a repository to store the requirements files (Doorstop, >>> YAML). This is the first thing we have to know. If it later turns out that >>> the >>> choice was bad, we can still remove it from one repository and do a subtree >>> import in another. >> I suggest you use personal repos under your name to experiment with. It will >> give you more freedom and will not impact on the main repos until we know the >> direction. > > Yes, we can do this. The drawback with this approach is that the work is a bit > more detached from the RTEMS development and will probably end up with a huge > patch set out of nothing.
If we start with a single component and go from there we can monitor how it is evolving. If the approach is sensible, scalable and we like it we can move to the main repo. I assume you will post patches for view? I recommend this happens because a large merge becomes a simple move to the main repo. Yes buildbot will go nuts but we can discuss this Amar when the time comes. Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
