From: Michal Marek <mmarek@suse.com>
To: Anton Tikhomirov <anton.tikhomirov@cdnetworks.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild/mkspec: avoid using brace expansion
Date: Sun, 11 Dec 2016 11:00:42 +0100 [thread overview]
Message-ID: <20161211100042.GA30135@sepie.suse.cz> (raw)
In-Reply-To: <20161025090041.GA4423@cdnetworks.com>
On Tue, Oct 25, 2016 at 06:00:44PM +0900, Anton Tikhomirov wrote:
> Brace expansion might not work properly if _buildshell RPM macro
> points to a shell other than bash. Particularly, with _bulidshell
> defined to /bin/dash it leads to broken build and source symlinks.
>
> Signed-off-by: Anton Tikhomirov <anton.tikhomirov@cdnetworks.com>
> ---
> scripts/package/mkspec | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Applied to kbuild.git#misc, thanks.
Michal
prev parent reply other threads:[~2016-12-11 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 9:00 [PATCH] kbuild/mkspec: avoid using brace expansion Anton Tikhomirov
2016-12-11 10:00 ` Michal Marek [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=20161211100042.GA30135@sepie.suse.cz \
--to=mmarek@suse.com \
--cc=anton.tikhomirov@cdnetworks.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).