Displaying 2 results from an estimated 2 matches for "bashiop".
Did you mean:
bashing
2013 Oct 09
0
[PATCH 0/1] Porting klibc to arm64
...ck.t:integer-base-one-3As
pass ./check.t:integer-base-one-3Ws
pass ./check.t:integer-base-one-3Ar
pass ./check.t:integer-base-one-3Wr
pass ./check.t:integer-base-one-4
pass ./check.t:integer-base-one-5A
pass ./check.t:integer-base-one-5W
pass ./check.t:ulimit-1
pass ./check.t:redir-1
pass ./check.t:bashiop-1
pass ./check.t:bashiop-2a
pass ./check.t:bashiop-2b
pass ./check.t:bashiop-2c
pass ./check.t:bashiop-3a
pass ./check.t:bashiop-3b
pass ./check.t:bashiop-4
pass ./check.t:mkshiop-1
pass ./check.t:mkshiop-2
pass ./check.t:oksh-shcrash
pass ./check.t:oksh-varfunction-mod1
pass ./check.t:fd-cloexec-1...
2013 Oct 09
2
[PATCH 0/1] Porting klibc to arm64
On Wed, 9 Oct 2013 10:44:27 +0000 (UTC)
Thorsten Glaser <tg at mirbsd.de> wrote:
> Anil Singhar dixit:
>
> >Manual testing as provided within the package has been done with all
> >tests passing. This includes the units tests available under
> >usr/klibc/tests, usr/utils, usr/dash and usr/gzip. For dash and
> >gzip, only sanity testing has been done.
>
>