Michael Shigorin 025e611057 mktmpdir: fixed sort key ... The sort key field value has been off-by-one apparently, "6" corresponds to "capacity" field of df -PT output while the "available" one was meant: Filesystem Type 1024-blocks Used Available Capacity Mounted on /dev/sda9 ext4 15350768 12799972 1747980 88% / tmpfs tmpfs 1967204 27396 1939808 2% /tmp 1 2 3 4 5 6 This lapse has been five years old, looks like it's only been masked by lower available space limit *and* filesystem ordering by type so far. It didn't hit me even now, rather inspected the code while implementing volumes-profile-starterkit...		2015-09-07 21:01:14 +03:00
..
columnize	more readable `make help', finally	2012-04-02 17:16:27 +03:00
mktmpdir	mktmpdir: fixed sort key	2015-09-07 21:01:14 +03:00
mp-commit	fixed mp-commit and its use	2013-02-11 21:29:15 +04:00
mp-showref	git usage refactoring	2012-08-10 00:12:46 +03:00
pkgdups	READMEs: pkglist related clarification	2012-04-09 22:21:10 +03:00
report-filter	initial target tracing support and reporting	2012-03-19 19:23:38 +02:00
report-targets	report-targets: process vm/* either	2013-07-02 00:01:38 +04:00
report-targets2vars	initial target tracing support and reporting	2012-03-19 19:23:38 +02:00
tags2lists	tags2lists: skip backup files too	2014-01-16 15:52:12 +04:00
tar2fs	tar2fs: fixed broken sfdisk use	2015-05-31 18:08:19 +03:00