On 06/23/2012 12:30 PM, intrigeri wrote: > Hi, > > Ben Hutchings wrote (23 Jun 2012 19:02:06 GMT) : >> What is it that you think will happen at the freeze? We stop fixing >> all bugs and do nothing for the next few months? > > Of course, and we'll lazily eat lots of icecream while you work hard > to release many shiny new Linux 3.2.x :) > > Irony set aside, I believe there are two different ways of fixing this > bug: > > - Either by fixing the actual regression directly, without applying > the network control patch: it seems clear to me that this can > happen after the freeze. So far, so good. > > - Or by applying the AppArmor network control patch, in an improved > version that John is apparently working on; this would be my > preferred solution. But, given it would be a feature addition, > rather than being merely a minimal bugfix, I'm not too sure it > would be fit for a freeze exception. Hence my gentle pressuring on > John to get this done before the freeze. > > Feel free to correct me if my understanding of the situation is wrong. > To be clear the network stuff I am working on for wheezy is 2 patches to the current networking patch. The larger networking rewrite is not ready yet and even if I could get it done in time I would not feel comfortable pushing that in to wheezy as it would be at best early beta quality
-- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fe629f3.5010...@canonical.com
