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
..
corpus/seed/logsrvd_conf	Work around a glibc regcomp() bug with repeated '+' operators.	2022-02-01 13:12:19 -07:00
fuzz	Use #include <foo.h> instead of #include "foo.h" in most cases.	2023-09-25 10:13:28 -06:00
logsrvd_conf	Use #include <foo.h> instead of #include "foo.h" in most cases.	2023-09-25 10:13:28 -06:00