John Baldwin 1e2ec671fc Consistently use both leading and trailing spaces inside of the {}'s ... when pretty-printing structures. Most structures used both spaces, but some only used a trailing space and some used neither.		2015-08-06 20:05:40 +00:00
..
amd64-fbsd32.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
amd64-fbsd.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
amd64-linux32.c
amd64linux32.conf
arm-fbsd.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
extern.h
fbsd32.conf
i386-fbsd.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
i386-linux.c
i386.conf
i386linux.conf
main.c
Makefile
Makefile.depend.amd64
mips-fbsd.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
powerpc64-fbsd.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
powerpc-fbsd.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
setup.c
sparc64-fbsd.c	truss: follow pdfork()ed descendents with -f	2015-07-24 16:57:13 +00:00
syscall.h	Decode the arguments passed to the *at() family of system calls. This is	2015-08-06 19:08:33 +00:00
syscalls.c	Consistently use both leading and trailing spaces inside of the {}'s	2015-08-06 20:05:40 +00:00
truss.1
truss.h