Dec 17 2018
Sorry for the duplicate revision. I'm having curl problems.
Mar 13 2018
Jan 20 2018
Dec 28 2017
Dec 23 2017
Man: start a sentence from new line.
Add CAVEATS section to the man page to point out the rounding issue with too short buffers.
Dec 22 2017
Thank you for patch.
I apply this patch to 12.0-CURRENT r327074, the right value is shown with ls -lh.
Dec 21 2017
Address @cem comments about style(9).
I don't understand the actual algorithmic change, but given the strong test coverage, I think I'm ok with this. Some style nits below.
Jun 11 2017
Apr 20 2016
Dec 2 2015
Nov 20 2015
Nov 19 2015
They already see it, they just don't know what to do once they are there.
No, I don't want this in `/usr/share/docs`. This is meant to be *newbie* friendly so people can just go in /usr/tests
and figure out what to do relatively quickly by looking at the README.
The way to figure this out right now is confusing enough as it is with info scattered all over the place in different man pages,
wikis, etc. The end result is that newbies can't figure out what to do, and keep asking me.
It seems like this should be installed to /usr/share/docs
Nov 5 2015
Oct 19 2015
This is extremely ugly. For my tests, the function is the same, but the arguments are what produce the test case. In essense, I have to either retype the same thing twice, or create a wrapper that would call ATF_CHECK_MSG() only in case of failure.
Sidenote: the only thing that's slightly painful with ATF that other test infrastructures seem to do better is that ATF_CHECK/ATF_REQUIRE don't print out the result of the expression, so if you need to dump out the result of the check, use ATF_CHECK_MSG/ATF_REQUIRE_MSG instead, like:
Do not create temp file in /tmp. Use ATF_CHECK instead of ATF_CHECK_EQ.
Add VM_MAXUSER + 1, 0 test.
Is it worth checking VM_MAXUSER_ADDRESS + 1, 0?