[PATCH 0/2] Use the new ash_msg_and_raise_perror() in more places
Johannes Schindelin
johannes.schindelin at gmx.de
Tue Aug 22 20:03:13 UTC 2017
This is by no means an exhaustive list of patches where using the
*_perror() instead of the *_error() function would make sense. Yet, I
encountered both errors in my development and really needed to get a
better idea what was wrong than, say, "can't cd to ...".
Hopefully these patches are useful for other developers, too.
Johannes Schindelin (2):
ash: report reason when a script file could not be opened
ash: when cd fails, say why
shell/ash.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
base-commit: 3505e38bd1e5714fa1203e6752c573861aab8521
Published-As: https://github.com/dscho/busybox-w32/releases/tag/busybox-report-errors-v1
Fetch-It-Via: git fetch https://github.com/dscho/busybox-w32 busybox-report-errors-v1
--
2.14.1.windows.1.11.gc06fee21d46.dirty
More information about the busybox
mailing list