From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>,
Srinuvasan A <srinuvasan.a@siemens.com>
Subject: Re: [isar-cip-core][PATCH] scripts: Address shellcheck findings
Date: Wed, 5 Apr 2023 11:41:29 +0200 [thread overview]
Message-ID: <eb7f3f88-4ea1-d14f-73e2-87a32fb2b8c0@siemens.com> (raw)
In-Reply-To: <c8486cd6-5a5b-d556-0bc0-71d22472e8ea@siemens.com>
On 05.04.23 11:38, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Mostly quoting warnings, but also a non-functional stderr>stdout
> redirection.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
Sorry, wrong list once again.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
prev parent reply other threads:[~2023-04-05 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 9:38 Jan Kiszka
2023-04-05 9:41 ` Jan Kiszka [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=eb7f3f88-4ea1-d14f-73e2-87a32fb2b8c0@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=quirin.gylstorff@siemens.com \
--cc=srinuvasan.a@siemens.com \
/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