Andrew Morton wrote:
What I'm concerned about is that regressions which we didn't fix are just getting lost. Is anyone taking care to ensure that they are getting transitioned into bugzilla for tracking?
Maybe this was a dumb assumption on my part, but I thought regressions were getting rolled over into the next release's list, if they are not solved?
Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- nmi_watchdog=2 regression in 2.6.21
- From: Daniel Walker <[email protected]>
- Re: nmi_watchdog=2 regression in 2.6.21
- From: Björn Steinbrink <[email protected]>
- Re: nmi_watchdog=2 regression in 2.6.21
- From: Daniel Walker <[email protected]>
- Re: nmi_watchdog=2 regression in 2.6.21
- From: Michal Piotrowski <[email protected]>
- Re: nmi_watchdog=2 regression in 2.6.21
- From: Daniel Walker <[email protected]>
- Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)
- From: Michal Piotrowski <[email protected]>
- Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)
- From: Andrew Morton <[email protected]>
- nmi_watchdog=2 regression in 2.6.21
- Prev by Date: Re: PROBLEM : On a laptop Aopen 1556 or 1557 my integrated card-reader doesn't work.
- Next by Date: Re: RFC: issues concerning the next NAPI interface
- Previous by thread: Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)
- Next by thread: Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)
- Index(es):