We rushed binutils/gcc5 into 16.03 to get it there in time. It's far from
ideal, but
please open issue if something is not working on 16.03.
On Tue, Mar 22, 2016 at 3:07 PM, Lluís Batlle i Rossell
wrote:
> On Tue, Mar 22, 2016 at 02:10:44PM +0100, joach...@fastmail.fm wrote:
> > On Tue, Mar 22,
On Tue, Mar 22, 2016 at 02:10:44PM +0100, joach...@fastmail.fm wrote:
> On Tue, Mar 22, 2016, at 01:59 PM, Lluís Batlle i Rossell wrote:
> > How weird. Why that was merged into 16.03 and not into master? Why isn't
> > master the first step to 16.03?
>
> Because releases are linux only and so are u
On Tue, Mar 22, 2016, at 01:59 PM, Lluís Batlle i Rossell wrote:
> On Tue, Mar 22, 2016 at 01:23:39PM +0100, Vladimír Čunát wrote:
> > On 03/22/2016 10:22 AM, Lluís Batlle i Rossell wrote:
> > > I think that someone merged into 16.03 instead of into master unwillingly.
> > > An error. But did this
On Tue, Mar 22, 2016 at 01:23:39PM +0100, Vladimír Čunát wrote:
> On 03/22/2016 10:22 AM, Lluís Batlle i Rossell wrote:
> > I think that someone merged into 16.03 instead of into master unwillingly.
> > An error. But did this pass unnoticed by the maintainers for more than 15
> > days?
>
> No, acc
On 03/22/2016 10:22 AM, Lluís Batlle i Rossell wrote:
> I think that someone merged into 16.03 instead of into master unwillingly.
> An error. But did this pass unnoticed by the maintainers for more than 15
> days?
No, according to some chats the inclusion in 16.03 is intentional. The
changes for
On Tue, Mar 22, 2016 at 10:12:39AM +0100, Pascal Wittmann wrote:
> On 03/22/2016 09:56 AM, Lluís Batlle i Rossell wrote:
> > why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master
> > in gcc 4.9?
> >
> > I don't understand. Should we put fixes for gcc5 builds into 16.03 and not
On 03/22/2016 09:56 AM, Lluís Batlle i Rossell wrote:
> why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master
> in gcc 4.9?
>
> I don't understand. Should we put fixes for gcc5 builds into 16.03 and not
> master?
I noticed that too when fixing some builds on release-16.03, but
Hello,
why is release-16.03 in gcc 5.3 (hardening+staging merged in), and master
in gcc 4.9?
I don't understand. Should we put fixes for gcc5 builds into 16.03 and not
master?
--
(Escriu-me xifrat si saps PGP / Write ciphered if you know PGP)
PGP key D4831A8A - https://emailselfdefense.fsf.org/
