From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: nick <xerofoify@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Time To Build Yocto
Date: Wed, 22 Oct 2014 16:07:37 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1410221602280.4422@localhost> (raw)
In-Reply-To: <54457446.5090809@gmail.com>
On Mon, 20 Oct 2014, nick wrote:
> I am wondering from your experience how long is the largest build
> you have ever seen and what was it building. I am considering a high
> powered build system for Yocto and want to known about build times
> in order to help me with purchasing decisions.
dear yocto mailing list:
at the risk of sounding heartless, please don't feed the troll. nick
krause is notorious from the kernel and kernel newbie mailing lists as
someone who, desperate to get his name into the git log as a kernel
developer, has pissed off pretty much *everyone* by submitting
badly-formed, ill-considered patches against numerous subsystems, to
the point where he was finally *banned* from LKML. that didn't slow
him down, as he simply joined the kernel newbies ML and did exactly
the same thing there.
this is nick:
http://www.themukt.com/2014/08/04/someone-trolling-linux-kernel-mailing-lists-really-hard/
it remains to be seen if nick has changed his ways at all -- i am
simply posting this as a public service announcement so you know what
you might be getting into.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2014-10-22 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 20:44 Time To Build Yocto nick
2014-10-22 19:59 ` Chris Tapp
2014-10-22 22:25 ` nick
2014-10-22 20:07 ` Robert P. J. Day [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=alpine.LFD.2.11.1410221602280.4422@localhost \
--to=rpjday@crashcourse.ca \
--cc=xerofoify@gmail.com \
--cc=yocto@yoctoproject.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.