From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
akuster808 <akuster808@gmail.com>
Subject: Re: [rocko] Go fixups
Date: Thu, 07 Dec 2017 12:30:36 +0000 [thread overview]
Message-ID: <1512649836.19417.76.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKq14eNanqVJpXDyRdtr=fd_W5_7r6MhjAztVmg5FGbn7g@mail.gmail.com>
On Wed, 2017-12-06 at 09:28 -0200, Otavio Salvador wrote:
> Hello Armin,
>
> There was one patch which was mistakenly forgotten on rocko-next, and
> ended being merged. It ended being reworked in master and I did the
> needed backports/revert in our repo[1].
>
> 1. https://github.com/OSSystems/oe-core/compare/rocko...rocko-next
>
> Please consider applying those soon as rocko is currently with a
> broken Go toolchain.
Thanks for this Otavio, it was much appreciated and I've merged it.
Cheers,
Richard
prev parent reply other threads:[~2017-12-07 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 11:28 [rocko] Go fixups Otavio Salvador
2017-12-06 12:19 ` Martin Jansa
2017-12-07 12:30 ` Richard Purdie [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=1512649836.19417.76.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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.