> On Jul 20, 2017, at 3:06 PM, Torsten Duwe <d...@suse.de> wrote: > > On Thu, Jul 20, 2017 at 01:58:06PM +0300, Maxim Kuvyrkov wrote: >>> On Jul 17, 2017, at 3:10 PM, Torsten Duwe <d...@suse.de> wrote: >>> >>> What is the next step now? Is anybody going to commit that patch? >> >> Torsten, if you prefer I can commit your patch (after bootstrap and a >> regtest on aarch64-linux-gnu and x86_64-linux-gnu). > > Ok, who is going to do that?
I'll do that, np. > >> There is one last hurdle to sort out with the FSF copyright assignment. >> Looking at FSF's list I don't see SuSe's copyright assignment for your >> contributions to FSF projects, of which GCC is one. You can either request >> SuSe to file a copyright assignment for you, or, probably simpler, ask one >> of your SuSe colleagues (Richard B., Jan H.) to commit under their >> assignment. > > From my understanding, it should not make a difference, as the copyright > owner is identical (SUSE). But I'm not going to argue on legal issues here. > Let's first see what the test outcome is. Thanks so far! SuSe/Novell choose to do its assignments per engineer, not for the whole company, so I don't think you are covered as is. -- Maxim Kuvyrkov www.linaro.org
