Openembedded Core Discussions
 help / color / mirror / Atom feed
* [rocko] Go fixups
@ 2017-12-06 11:28 Otavio Salvador
  2017-12-06 12:19 ` Martin Jansa
  2017-12-07 12:30 ` Richard Purdie
  0 siblings, 2 replies; 3+ messages in thread
From: Otavio Salvador @ 2017-12-06 11:28 UTC (permalink / raw)
  To: Patches and discussions about the oe-core layer, akuster808

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.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [rocko] Go fixups
  2017-12-06 11:28 [rocko] Go fixups Otavio Salvador
@ 2017-12-06 12:19 ` Martin Jansa
  2017-12-07 12:30 ` Richard Purdie
  1 sibling, 0 replies; 3+ messages in thread
From: Martin Jansa @ 2017-12-06 12:19 UTC (permalink / raw)
  To: Otavio Salvador; +Cc: Patches and discussions about the oe-core layer

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

Thanks,

this will most likely fix the issue I've reported earlier in:
http://lists.openembedded.org/pipermail/openembedded-core/2017-December/145278.html
as well.

On Wed, Dec 6, 2017 at 12:28 PM, Otavio Salvador <
otavio.salvador@ossystems.com.br> 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.
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 2086 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [rocko] Go fixups
  2017-12-06 11:28 [rocko] Go fixups Otavio Salvador
  2017-12-06 12:19 ` Martin Jansa
@ 2017-12-07 12:30 ` Richard Purdie
  1 sibling, 0 replies; 3+ messages in thread
From: Richard Purdie @ 2017-12-07 12:30 UTC (permalink / raw)
  To: Otavio Salvador, Patches and discussions about the oe-core layer,
	akuster808

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-12-07 12:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox