From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] rpm: run binary package generation via thread pools
Date: Mon, 12 Jun 2017 18:02:15 +0300 [thread overview]
Message-ID: <c1bdfae3-8ee8-a281-413b-e56083480097@linux.intel.com> (raw)
In-Reply-To: <20170612145805.11599-1-alexander.kanavin@linux.intel.com>
On 06/12/2017 05:58 PM, Alexander Kanavin wrote:
> This greatly reduces build times when there is a large amount of small
> rpm packages to produce. The patches are rather invasive,
> and so will be submitted upstream.
The changes in this version of the patch:
- fixed (hopefully) the segfaults seen on autobuilder with older
versions of gcc
- made sure that build host and build time are set only once, and are
the same in all output files.
Alex
next prev parent reply other threads:[~2017-06-12 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 14:58 [PATCH] rpm: run binary package generation via thread pools Alexander Kanavin
2017-06-12 15:01 ` ✗ patchtest: failure for " Patchwork
2017-06-12 15:02 ` Alexander Kanavin [this message]
2017-06-12 19:29 ` [PATCH] " Leonardo Sandoval
2017-06-13 16:15 ` Leonardo Sandoval
2017-06-13 16:13 ` Alexander Kanavin
2017-06-13 16:43 ` Leonardo Sandoval
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=c1bdfae3-8ee8-a281-413b-e56083480097@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.