[<prev] [next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2009140821041.2357@hadrien>
Date: Mon, 14 Sep 2020 08:21:23 +0200 (CEST)
From: Julia Lawall <julia.lawall@...ia.fr>
To: Markus Elfring <Markus.Elfring@....de>
cc: Sumera Priyadarsini <sylphrenadin@...il.com>,
Coccinelle <cocci@...teme.lip6.fr>,
Michal Marek <michal.lkml@...kovi.net>,
Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Cocci] [RFC PATCH] scripts: coccicheck: Improve error feedback
when coccicheck fails
On Mon, 14 Sep 2020, Markus Elfring wrote:
> …
> > +++ b/scripts/coccicheck
> > @@ -126,8 +126,14 @@ run_cmd_parmap() {
> > if [ $VERBOSE -ne 0 ] ; then
> > echo "Running ($NPROC in parallel): $@"
> > fi
> > - echo $@ >>$DEBUG_FILE
> > - $@ 2>>$DEBUG_FILE
> > + if [ "$DEBUG_FILE" != "/dev/null" -a "$DEBUG_FILE" != "" ]; then
> …
>
> How do you think about to use the following check variant?
>
> + if [ "${DEBUG_FILE}" != '/dev/null' -a "${DEBUG_FILE}" != '' ]; then
What difference does it make?
julia
Powered by blists - more mailing lists