fwiw, I prefer more expressive subject lines, makes it easier to immediately
identify commits in the log. specifically always include the 'topic' of the
patch target, e.g. test, tools, touchpad, timer, etc. so in your case:
test: handle getcwd() and system() return values in litest
or something
Added code to check for errors in getcwd() and system() that
were previously ignored and silently dropped.
Signed-off-by: Jon A. Cruz
---
test/litest.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/test/litest.c b/test/litest.c
index 349eca0..e658c32 10064
