Displaying 2 results from an estimated 2 matches for "utf8bom".
2013 Oct 09
0
[PATCH 0/1] Porting klibc to arm64
...shrc-2b
pass ./check.t:mkshrc-3
pass ./check.t:sh-mode-1
pass ./check.t:sh-mode-2a
pass ./check.t:pipeline-1
pass ./check.t:pipeline-2
pass ./check.t:pipeline-3
pass ./check.t:persist-history-1
pass ./check.t:typeset-1
pass ./check.t:typeset-padding-1
pass ./check.t:typeset-padding-2
pass ./check.t:utf8bom-1
pass ./check.t:utf8bom-2
pass ./check.t:utf8opt-1a
pass ./check.t:utf8opt-2a
pass ./check.t:utf8opt-3a
pass ./check.t:utf8opt-3b
pass ./check.t:aliases-1
pass ./check.t:aliases-2b
pass ./check.t:aliases-3b
pass ./check.t:aliases-cmdline
pass ./check.t:aliases-funcdef-1
pass ./check.t:aliases-func...
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.
>
>