sudo/lib/util/regress/sudo_parseln
Todd C. Miller e343e07543 Use #include <foo.h> instead of #include "foo.h" in most cases.
We rely on the include path to find many of these headers.  It
especially doesn't make sense to use #include "foo.h" for headers
in the top-level include directory.
2023-09-25 10:13:28 -06:00
..
parseln_test.c Use #include <foo.h> instead of #include "foo.h" in most cases. 2023-09-25 10:13:28 -06:00
test1.in Apply Google inclusive language guidelines. 2020-10-30 10:15:30 -06:00
test1.out.ok Top level directory reorg 2014-06-26 15:51:02 -06:00
test2.in Top level directory reorg 2014-06-26 15:51:02 -06:00
test2.out.ok Top level directory reorg 2014-06-26 15:51:02 -06:00
test3.in Top level directory reorg 2014-06-26 15:51:02 -06:00
test3.out.ok Top level directory reorg 2014-06-26 15:51:02 -06:00
test4.in Top level directory reorg 2014-06-26 15:51:02 -06:00
test4.out.ok Top level directory reorg 2014-06-26 15:51:02 -06:00
test5.in Top level directory reorg 2014-06-26 15:51:02 -06:00
test5.out.ok Top level directory reorg 2014-06-26 15:51:02 -06:00
test6.in Top level directory reorg 2014-06-26 15:51:02 -06:00
test6.out.ok Top level directory reorg 2014-06-26 15:51:02 -06:00