Thread (1 message) 1 message, 1 author, 2018-09-13

Re: [PATCH 1/1] contrib: add coverage-diff script

From: Junio C Hamano <hidden>
Date: 2018-09-13 14:59:58

Derrick Stolee [off-list ref] writes:
On 9/12/2018 6:54 PM, Junio C Hamano wrote:
quoted
Junio C Hamano [off-list ref] writes:
quoted
"Derrick Stolee via GitGitGadget" [off-list ref] writes:
quoted
  contrib/coverage-diff.sh | 70 ++++++++++++++++++++++++++++++++++++++++
  1 file changed, 70 insertions(+)
  create mode 100755 contrib/coverage-diff.sh
I fully appreciate the motivation.  But it is a bit sad that this
begins with "#!/bin/bash" but it seems that the script is full of
bash-isms.  I haven't gone through the script to see if these are
inevitable or gratuitous yet, but I'd assume it made it easier for
you to write it to step outside the pure POSIX shell?
I completely forgot to avoid bash, as I wrote this first as an experiment.
quoted
quoted
...
quoted
+	elif [[ $REPLY =~ \+\+\+\ (b/)?([^[:blank:]$esc]+).* ]]; then
+	    path=${BASH_REMATCH[2]}
OK, it probably is easier to write in bash than using expr if you
want to do regexp.
Just to clarify. I am saying that it is OK to give up writing in
pure POSIX and relying on bash-isms after seeing these lines.
I'll try rewriting it using POSIX shell and see how hard it is.
Thanks.  Don't waste too much time on it and try to bend backwards
too far, though.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help