On Mon, Sep 10, 2007 at 02:23:24AM -0700, Andrew Morton wrote:
> > And I think almost everyone disagrees with you. We just carry too much
> > crap around because of your subborness in this issue, and it gets really
> > annoying to have some high up on the food chain fighting his longly flight
> > against the other people.
>
> I would like to see "everyone" explain what we lose by giving developers a
> bit of warning before we break their stuff.
>
>
> And it would need to be a good explanation, Christoph. A measured one
> which recognises and then weighs the tradeoffs involved, and the costs. An
> inebriated-sounding rant will not impress, sorry.
Fine, then. Just how much of a warning is needed in this particular case?
Normally I'm the last one to support Adrian's exportectomy binges, but in
case of sys_open() it's _way_ overdue. There had been warnings for quite
a while; moreover, fixing the breakage in any case that is not already
badly broken is going to take a few minutes. People who had not found
spare ten minutes during the last few years have my sincere condolences,
but they bloody can do that when it hits the fan and I see no reason to
believe that a warning in build time or modprobe time would do more than
multiple warnings on maillists.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
