From: Paul Bolle <pebolle@tiscali.nl>
To: Sam Bobroff <sam.bobroff@au1.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] merge_config.sh: exit on missing input files
Date: Fri, 03 Jul 2015 13:25:03 +0200 [thread overview]
Message-ID: <1435922703.17390.3.camel@tiscali.nl> (raw)
In-Reply-To: <45b4e87ddc059dcddc36aa86649d2d52cc63da78.1435899816.git.sam.bobroff@au1.ibm.com>
On vr, 2015-07-03 at 15:03 +1000, Sam Bobroff wrote:
> Add a check for the existence of input files and exit (with failure)
> if they are missing.
>
> Without this additional check, missing files produce error messages
> but still result in an output file being generated and a successful
> exit code.
>
> Signed-off-by: Sam Bobroff <sam.bobroff@au1.ibm.com>
Could you please resend and include linux-kbuild@vger.kernel.org?
scripts/get_maintainer.pl would have told you that. (Please don't bother
including Yann Morin, as Yann has not been heard of for a long time
now.)
Thanks,
Paul Bolle
prev parent reply other threads:[~2015-07-03 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 5:03 Sam Bobroff
2015-07-03 11:25 ` Paul Bolle [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=1435922703.17390.3.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sam.bobroff@au1.ibm.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
all inboxes | Powered by JetHome®