On Tue, May 3, 2011 at 11:32, Charles Plessy <ple...@debian.org> wrote: > However, given my experience of repetitive patching cycles with earlier GCC > updates, it would be pointless to spend a lot of energy updating our packages > now if it is only to realise in few weeks that the next GCC update would > require yet another header. > > So can we have some perspectives and gross time frame, sent on > debian-devel-announce@l.d.o, that we could also use as a reference when we > will > forward the issue to our upstreams ? For the packages I maintain, I would > prefer to see – and help – these bugs fixed by new upstream release rather > than > by patch.
Who do you expect to send such communication? the gcc maintainer? good luck with that. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktiktemvmn4xljhiqcbp5yglgsm1...@mail.gmail.com
