From: Trevor Woerner <twoerner@gmail.com>
To: akuster808 <akuster808@gmail.com>
Cc: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Subject: Re: World builds
Date: Thu, 8 Feb 2018 14:55:43 -0500 [thread overview]
Message-ID: <20180208195543.GA29027@linux-uys3> (raw)
In-Reply-To: <bbc09ab4-1bc7-3120-5de5-0bf02636c629@gmail.com>
Hi Armin,
On Mon 2018-02-05 @ 08:19:56 AM, akuster808 wrote:
> There will be delays merging changes into meta-openembedded. One of
> our two build nodes has go off-line again. This the second time in a
> week it has happened.
Thanks for the update.
This makes me curious to know a bit more about how the world builds are done.
Can you give details about these nodes? What are they? Where are the hosted?
How pays their electricity?
> I am currently running basic world builds on my home system.
Is your home machine beefy enough? Is there a way to divide up the world build
so members of the community to volunteer to run some parts of the build?
Best regards,
Trevor
prev parent reply other threads:[~2018-02-08 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 2:49 World builds akuster808
2018-02-08 19:55 ` Trevor Woerner [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=20180208195543.GA29027@linux-uys3 \
--to=twoerner@gmail.com \
--cc=akuster808@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox