• Michael Shigorin's avatar
    no build means *no* build (and less reports), really · 454e7162
    Michael Shigorin authored
    It's hard to tell a successful build from a failed one
    if downstream hides the exit code; it's useless to continue
    a `for' loop if a pipe shoves that to a subshell; well it seems
    that a bashism is worth a thousand quirks with extra fds here.
    Minor regexp enhancements are also due.
    
    reports.mk made a bit more resilient/prudent either.
    454e7162
Name
Last commit
Last update
.gear Loading commit data...
bin Loading commit data...
conf.d Loading commit data...
doc Loading commit data...
features.in Loading commit data...
image.in Loading commit data...
lib Loading commit data...
pkg.in Loading commit data...
sub.in Loading commit data...
.gitignore Loading commit data...
COPYING Loading commit data...
Makefile Loading commit data...
QUICKSTART Loading commit data...
README Loading commit data...
main.mk Loading commit data...
reports.mk Loading commit data...