From: "Lock, Joshua G" <joshua.g.lock@intel.com>
To: "gmane@reliableembeddedsystems.com"
<gmane@reliableembeddedsystems.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Cc: "robert.berger@reliableembeddedsystems.com"
<robert.berger@reliableembeddedsystems.com>
Subject: Re: [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests
Date: Thu, 13 Oct 2016 21:29:35 +0000 [thread overview]
Message-ID: <1476394173.3034.13.camel@intel.com> (raw)
In-Reply-To: <35ab47fa82f7707f84e445919ddbbef5@reliableembeddedsystems.com>
Can you help me understand why you needed to create this patch?
We've run into some issues recently where toolchains we expected to be
built weren't and the PublishArtifacts buildstep failing because
they're missing is useful. With this change we'll no longer get that,
right?
Thanks,
Joshua
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2016-10-13 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 6:44 [yocto-autobuilder][PATCH] PublishArtifacts.py: deal only with built toolchains, cp also md5 and manifests gmane
2016-10-12 14:28 ` Bill Randle
2016-10-12 15:22 ` Beth 'pidge' Flanagan
2016-10-12 15:29 ` Beth 'pidge' Flanagan
2016-10-13 21:40 ` Joshua Lock
2016-10-13 21:29 ` Lock, Joshua G [this message]
2016-10-13 22:38 ` gmane
2016-10-14 9:27 ` Joshua Lock
2016-10-14 9:33 ` gmane
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=1476394173.3034.13.camel@intel.com \
--to=joshua.g.lock@intel.com \
--cc=gmane@reliableembeddedsystems.com \
--cc=robert.berger@reliableembeddedsystems.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.