Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Lisandro Damián Nicanor Pérez Meyer
On miércoles, 11 de enero de 2017 10:35:37 ART Sam Hartman wrote: [snip] > that was to doko not you. Usual me I'm afraid. I suscribed to the bug and forgot to see the To field. > I'd be happy to chat, but you've articulated your position fairly well. > If there's stuff not in the bug you'd like

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Sam Hartman
> "Lisandro" == Lisandro Damián Nicanor Pérez Meyer > writes: Lisandro> On miércoles, 11 de enero de 2017 09:39:25 ART Sam Hartman wrote: >> Hi. >> >> As you are probably aware, the question of what to do about >> linking on mips and stretch

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Lisandro Damián Nicanor Pérez Meyer
On miércoles, 11 de enero de 2017 11:49:48 ART Lisandro Damián Nicanor Pérez Meyer wrote: [snip] > I'll be online from 17:30 UTC onwards, nick lisandro on freenode. And also oftc, of course. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Lisandro Damián Nicanor Pérez Meyer
On miércoles, 11 de enero de 2017 09:39:25 ART Sam Hartman wrote: > Hi. > > As you are probably aware, the question of what to do about linking on > mips and stretch has been referred to the TC. > There's a reasonable probability that we're going to want to move very > quickly on this issue, and

Bug#850887: TC Involvement: MIPS and binutils

2017-01-11 Thread Sam Hartman
Hi. As you are probably aware, the question of what to do about linking on mips and stretch has been referred to the TC. There's a reasonable probability that we're going to want to move very quickly on this issue, and I wanted to reach out to you and see how we could best work with you to