[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#705169: RFH: iproute2 -- networking and traffic control tools



On Thu, 2013-04-11 at 10:45 +0200, Andreas Henriksson wrote:
> Hello Ben!
> 
> On Thu, Apr 11, 2013 at 03:09:15AM +0100, Ben Hutchings wrote:
> > On Wed, 2013-04-10 at 21:33 +0200, Andreas Henriksson wrote:
> [...]
> > > Triaging bugs listed at http://bugs.debian.org to find out if
> > > they are still valid, a fix can be found (and submitted upstream!),
> > > or confirmed to be in the kernel (and reassigned).
> > > 
> > > Following up on new bug reports. Potentially review and forward
> > > patches upstream.
> > [...]
> > 
> > I may be able to provide some help with this.  I've made occasional
> > contributions to upstream development, and I'm fairly familiar with the
> > kernel side of rtnetlink.
> 
> If you have time for this that would be awesome!
> My impression is that most iproute bugs are actually bugs inside
> the kernel networking stack. I didn't want to reassign stuff blindly though
> just to dump them somewhere else where they'll be forgotten.
> 
> I've previously tried to do agressive bug triaging and I hope the result
> is that you'll now find most bugs are either longstanding probably-valid
> bugs (and you should be able to tell from the subject line already if
> it's a minor thing like manpage updates requests).

I reassigned several, but I think the remainder are now genuine bugs in
iproute2.  Some of the documentation bugs may require input from kernel
developers.  For the longstanding tc questions, you could ask Jamal Hadi
Salim <jhs@mojatatu.com> as I think he did most of the kernel work.

Ben.

-- 
Ben Hutchings
All extremists should be taken out and shot.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: