Hello Sebastian,
On 2/9/21 3:14 PM, Sebastian Huber wrote:
> On 09/02/2021 15:10, Gedare Bloom wrote:
>
>> On Tue, Feb 9, 2021 at 7:07 AM Sebastian Huber
>> <sebastian.hu...@embedded-brains.de> wrote:
>>> On 09/02/2021 15:04, Gedare Bloom wrote:
>>>
>>>>> We are responsible to monitor the RTEMS development during the
>>>>> pre-qualification activity and adjust the specification, etc. I would
>>>>> have sent you an e-mail that a specification update is necessary. The
>>>>> basedefs is an area with a higher probability of changes.
>>>>>
>>>> Is there a sustainable plan for beyond the project lifetime (maybe,
>>>> something we need to discuss separately)? Is there a plan/way to
>>>> automate consistency checking or to clue a developer that there is a
>>>> possible related spec file to consider updating?
>>>>
>>> I think this is something for the how-to section:
>>>
>>> https://docs.rtems.org/branches/master/eng/req/howto.html
>>>
>>> For example, I added/changed an interface specification item, what
>>> should I do next?
>>>
>> Yes, I was just wondering if we can automate/script any checks to help
>> us think less.
> The goal is to get some script support in the future, however, the
> specification is still not complete enough to get useful results at the
> moment. The script could give you for example an indication which other
> items are affected if some item is changed.
I would already be happy if, for example, for the whole of the basedefs
(i.e. for all interfaces and requirements) I would have a place to store
the git-hash of the version I last updated the basedefs as well as the
list of most important files. Then I could later do the following to
figure out if there were any relevant changes which I need to take care of:
$ cd rtems
$ git pull
$ git diff <HASH-OF-LAST-UPDATE> HEAD <LIST-OF-RELEVANT-FILES>
where for the basedefs for example:
HASH-OF-LAST-UPDATE = 766009b4f19ecdb7f193c683ca60d6d8570f15c5
LIST-OF-RELEVANT-FILES = cpukit/include/rtems/score/basedefs.h \
testsuites/sptests/spmisc01/init.c
Greetings
fk
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
