From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] squashfs: update site to git.kernel.org
Date: Thu, 28 Jul 2016 15:02:47 +0200 [thread overview]
Message-ID: <20160728150247.6672f9ef@free-electrons.com> (raw)
In-Reply-To: <CANQCQpY3ZRoWL96QyHKNNrsOhocnAc_Zgr4-btghdGqCfDVb1A@mail.gmail.com>
Hello,
On Thu, 28 Jul 2016 07:59:46 -0500, Matthew Weber wrote:
> > Yeah, but they haven't made any release since the last one available
> > from sourceforge. Are they planning on doing a new release? What is the
> > motivation from moving from a stable release to some seemingly random
> > Git commit?
> >
> We pulled in that latest hash to fix a threading issue that we were seeing
> on our large build machines. When creating images with 64 cores we would
> sometimes get corrupted images that would fail to boot.
OK. Exactly the type of explanation that would have been good to have
in the commit log :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-28 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 21:32 [Buildroot] [PATCH] squashfs: update site to git.kernel.org Matt Weber
2016-07-28 8:08 ` Thomas Petazzoni
2016-07-28 12:59 ` Matthew Weber
2016-07-28 13:02 ` Thomas Petazzoni [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=20160728150247.6672f9ef@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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