Szabolcs Nagy <nsz@...t70.net> writes:

> over the next month im only in front of a computer sporadically

> but code style or quality of tests are less strict than for libc,
> so i dont expect many iterations. just post the patches so when i
> can take a look i can comment or apply them.

> btw if there is a repo with a branch i can cherrypick from that
> is a bit easier for me than handling mails. then i think you
> dont even have to post "obvious" patches to the list. i can pick
> them from the branch.

That works well for us, here is our branch -
https://github.com/Boeing/libc-test/tree/boeing-staging-next-libc-test

This branch hasn't quite got every test we have written so far on it,
but it should be up to date within the next week.

Thanks,
Ryan Gardner