From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH v2] backports: significantly speed up build
Date: Mon, 23 Dec 2019 20:16:57 +0100 [thread overview]
Message-ID: <44e109a2685099f7382c38fed293e4dc42129c15.camel@sipsolutions.net> (raw)
In-Reply-To: <03a681ac-6394-2c33-aec4-a8b69f84fcdc@hauke-m.de>
On Mon, 2019-12-23 at 19:51 +0100, Hauke Mehrtens wrote:
> On 12/3/19 5:28 PM, Johannes Berg wrote:
> > On Tue, 2019-12-03 at 17:15 +0100, Johannes Berg wrote:
> > > If --eval is not supported, keep doing what we did before.
> >
> > It's a bit disconcerting that we have systems that run make 3.81 or
> > older, but apparently that's what happened?! That was released over 9
> > years ago, and --eval was added to the code base 10 years ago ...
> >
> > johannes
> This looks good, but I am not an bash expert.
Neither am I! I just noticed the speed problem :-)
Really though, this change isn't much related to bash, right? It just
passes the variables to the sub-make in a different way.
> Even RedHat 7.7 uses make 3.82, so I do not care about older versions
> any more.
Cool. We had some older ones around in our infrastructure ... working to
get rid of them :)
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2019-12-23 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 16:15 [PATCH v2] backports: significantly speed up build Johannes Berg
2019-12-03 16:28 ` Johannes Berg
2019-12-23 18:51 ` Hauke Mehrtens
2019-12-23 19:16 ` Johannes Berg [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=44e109a2685099f7382c38fed293e4dc42129c15.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
/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).