* Andrew Morton wrote:
> We dont' do that as much nowadays - there's a tendency to
hm, who does this - i've seen networking folks do it but does anyone
else do it? Such cases are _clear_ abuse of users and they'll do the
obvious thing: vote with their feet.
I only ask people to bisect it when all other avenues fail - and even
then i try to make it clear that bisection is just something they can
_optionally_ do to speed things up (it's never required), and that it's
a pure opt-in.
doing _kernel_ bisection is totally hard at the moment - it disrupts the
user way too much and causes many hours of work for most users. [
Requiring bisection for userspace projects might be more doable. (but
even there's it's wrong when it's not automated completely and where a
failure pattern is not deterministic.) ]
Ingo
--
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
