On 06.11.23 21:55, Chris Johns wrote:
On 6/11/2023 8:27 pm, Sebastian Huber wrote:
On 06.11.23 01:14, Chris Johns wrote:
On 4/11/2023 1:31 am, Sebastian Huber wrote:
On 03.11.23 15:08, Joel Sherrill wrote:
On Fri, Nov 3, 2023 at 3:58 AM Sebastian Huber
mailto:sebastian.hu...@embedded-brains.d
On 08.11.23 00:17, Gedare Bloom wrote:
On Mon, Nov 6, 2023 at 1:55 PM Chris Johns wrote:
On 6/11/2023 8:27 pm, Sebastian Huber wrote:
On 06.11.23 01:14, Chris Johns wrote:
On 4/11/2023 1:31 am, Sebastian Huber wrote:
On 03.11.23 15:08, Joel Sherrill wrote:
On Fri, Nov 3, 2023 at 3:58 AM Se
I thought you would "verify" a package by looking at the symbols that
end up included in the binary.
And then have some sort of mapping between the symbols <> tests <> requirements.
Any extra symbols not in the verification "database" would end up as a
flag that a new test / requirement needs made
On Mon, Nov 6, 2023 at 1:55 PM Chris Johns wrote:
>
> On 6/11/2023 8:27 pm, Sebastian Huber wrote:
> > On 06.11.23 01:14, Chris Johns wrote:
> >> On 4/11/2023 1:31 am, Sebastian Huber wrote:
> >>> On 03.11.23 15:08, Joel Sherrill wrote:
> On Fri, Nov 3, 2023 at 3:58 AM Sebastian Huber
>