slstatus - slstatus patches

Age	Commit message (Collapse)	Author
2019-02-07	Add FreeBSD support for netspeeds, entropy and ip components	Michael Buch

2018-07-08	Consistency with 80 char limit and breaks	Aaron Marcher

2018-07-07	Simplify format specifiers for uintmax_t	Aaron Marcher

2018-07-07	Change uint64_t to uintmax_t	Aaron Marcher

2018-07-06	entropy: Use POSIX types for format specifiers	Aaron Marcher

2018-07-06	entropy: Improve types	Aaron Marcher

2018-05-20	Refactor entropy.c	Laslo Hunhold

2018-05-06	entropy: Small fix	Aaron Marcher

2018-05-06	entropy: Port to OpenBSD	Aaron Marcher
	OpenBSD's entropy design is superior to Linux.
2018-05-01	Use indentation to increase readability	Laslo Hunhold
	Granted, this style is definitely not common, but for the short utility-functions of this program it's just the right choice. This provides great flexibility, such that in the long run, it will be possible to also share code between the OS-implementations. This also keeps the state-keeping at a minimum and makes it clearer which functions are implemented on which OS without having to jiggle around with too many files in the process.
2018-05-01	Revert component-split	Laslo Hunhold
	this reverts the commits from 92ab9ef52ebcb097add97d9f78e67ad1c1d6a6ec up to d42870d6ca7fb587b38f8cf6d6821ae33a53a696. After heavy consideration, the component split has more disadvantages than advantages, especially given there will be utility-functions sharing quite a lot of code that would then need to be duplicated, as it does not fit into the util.c due to its speciality. One big advantage of the component-wise build is readability, and without doubt, this was achieved here. This point will be addressed with a different approach that will be visible in the upcoming commits. One big disadvantage of the component build is the fact that it introduces state to the build process which is not necessary. Before its introduction, the only influencing factors where the system-defines __linux__ and __OpenBSD__. With the components, we are also relying on the output of uname(1). Additionally, if the os.mk is not present, make gives the output $ make Makefile:5: os.mk: No such file or directory make: *** No rule to make target 'os.mk'. Stop. This could easily be fixed by providing some sort of meta-rule for this file, however, it indicates the problem we have here, and this entire statefulness will heavily complicate packaging of this tool and makes the build process much more complex than it actually has to be.
2018-04-30	entropy: OS split	Quentin Rameau

2018-03-21	More robust preprocessor switches	Aaron Marcher
	Replace #ifdef with #if defined() and #elif with #elif defined() as it should only test if it is defined or not.
2018-03-18	Build Linux-only functions only on Linux	Aaron Marcher

2017-09-24	Move components into dedicated subdirectory	Laslo Hunhold
	This brings us a lot more tidiness.