freebsd-dev

History

Maxim Sobolev 1fab62b1e1 Refactor the regression test code by splitting huge monolithic C file into smaller pieces that are hopefully easier to understand and extend. This is to pave the ground for adding few more socket timestamp formats that I am working on here. No functional changes (I hope).		2016-12-05 17:21:04 +00:00
..
bsdbox	DIRDEPS_BUILD: Build crunchide for the host.	2016-09-01 23:52:25 +00:00
build	Add a few missed clang 3.9.0 files to OptionalObsoleteFiles.	2016-11-27 14:19:19 +00:00
bus_space	Add an example program (in Python) for the AMD Am79c900 (ILACC)	2015-08-02 21:24:03 +00:00
debugscripts	Assorted grammar, spelling and punctuation fixes.	2015-12-15 13:04:44 +00:00
diag	Fix LDADD/DPADD that should be LIBADD.	2015-12-04 03:17:47 +00:00
ifnet	* Handle ++x as well as x++ while converting.	2014-06-25 15:22:14 +00:00
kerneldoc	Remove the wl(4) driver and wlconfig(8) utility.	2016-08-19 22:27:14 +00:00
KSE	NO_MAN= has been deprecated in favor of MAN= for some time, go ahead	2014-04-13 05:21:56 +00:00
LibraryReport
regression	Refactor the regression test code by splitting huge monolithic C	2016-12-05 17:21:04 +00:00
sched	Add a dtrace script for collecting schedgraph data	2016-11-18 02:29:09 +00:00
test	Fix spelling and grammer in tools/test/README.	2015-10-28 15:00:21 +00:00
tools	Trying to autodetect legacy setups lead to problems when people	2016-11-28 21:29:01 +00:00
install.sh	Use -n to ln(1) which is compatible with GNU ln(1).	2015-11-16 23:27:44 +00:00
make_libdeps.sh	Avoid rs(1) hitting LINE_MAX with custom trees that have large dependencies.	2014-09-08 17:01:30 +00:00
README
tinder.sh	Remove the old depend (mkdep) code and make FAST_DEPEND the one true way.	2016-03-30 23:50:23 +00:00

README

$FreeBSD$

This directory tree contains tools used for the maintenance and
testing of FreeBSD.  There is no toplevel Makefile structure since
these tools are not meant to be built as part of the standard system,
though there may be individual Makefiles in some of the subdirs.

Please read the README files in the subdirs for further information.