From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netdev@vger.kernel.org
Subject: Re: [iproute PATCH v2 0/2] Covscan: Shell script fixes
Date: Fri, 18 Aug 2017 09:12:07 -0700 [thread overview]
Message-ID: <20170818091207.40bd4887@xeon-e3> (raw)
In-Reply-To: <20170817170932.24900-1-phil@nwl.cc>
On Thu, 17 Aug 2017 19:09:30 +0200
Phil Sutter <phil@nwl.cc> wrote:
> This series collects patches from v1 which deal with programming
> mistakes in shell scripts.
>
> No changes to the actual patches, just splitting into smaller series.
>
> Phil Sutter (2):
> examples: Some shell fixes to cbq.init
> ifcfg: Quote left-hand side of [ ] expression
>
> examples/cbq.init-v0.7.3 | 24 ++++++++++++------------
> ip/ifcfg | 2 +-
> 2 files changed, 13 insertions(+), 13 deletions(-)
>
Applied.
prev parent reply other threads:[~2017-08-18 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 17:09 [iproute PATCH v2 0/2] Covscan: Shell script fixes Phil Sutter
2017-08-17 17:09 ` [iproute PATCH v2 1/2] examples: Some shell fixes to cbq.init Phil Sutter
2017-08-17 17:09 ` [iproute PATCH v2 2/2] ifcfg: Quote left-hand side of [ ] expression Phil Sutter
2017-08-18 9:32 ` David Laight
2017-08-18 11:24 ` Phil Sutter
2017-08-18 16:38 ` David Laight
2017-08-18 16:12 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170818091207.40bd4887@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox