remove the v850 port
I can't afford to be critical here, but let me give a comment.
i think putting this in feature-removal-schedule.txt just good practice.
you give people the chance to catch up - sort of a last reminder to the devs "fix it or we need to drop it". some chance for the users to see it will go away and make early decision based on that.
i like those cleanup efforts, but even if it was announced on lkml, or elsewhere - that file is the official place for such announcements and if you want people take care of that file, there should be reliable information inside.
it often takes much effort and hard work to get code into the kernel, so some "nah, this is broken, doesn`t compile for long - put that to trash" seems a little bit harsh for me.
the reason why its broken is probably not the v850 peoples fault.
ok, they just didn`t catch up with that "kernel progress" - but most probably some other person broke their code.
i don`t like bureaucracy, but a little bit of bureaucracy at the right place is not that bad at all.....
roland
Quoted 6 lines
start by putting the intention of removal into:
Documentation/feature-removal-schedule.txtwe can remove it after that. Same for most of your other removal patches.
Why?
Quoted 1 line
Ingo
cu
Adrian
_________________________________________________________________________
In 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114
Quoted 6 lines · On Tue, Apr 22, 2008 at 01:38:49AM +0200, [email protected] wrote:
I can't afford to be critical here, but let me give a comment.
i think putting this in feature-removal-schedule.txt just good practice.
you give people the chance to catch up - sort of a last reminder to the devs "fix it or we need to drop it". some chance for the users to see it will go away and make early decision based on that.
Quoted 8 lines
i like those cleanup efforts, but even if it was announced on lkml, or elsewhere - that file is the official place for such announcements and if you want people take care of that file, there should be reliable information inside.
it often takes much effort and hard work to get code into the kernel, so some "nah, this is broken, doesn`t compile for long - put that to trash" seems a little bit harsh for me.
the reason why it
s broken is probably not the v850 peoples fault.
ok, they just didn`t catch up with that "kernel progress" - but most probably some other person broke their code.i don`t like bureaucracy, but a little bit of bureaucracy at the right place is not that bad at all.....
As the patch description says it does not even compile since at least kernel 2.6.19 (which was released in 2006).
I've sent this removal patch 7 times during 3 months to linux-kernel.
Before that I sent 2 emails to linux-kernel asking about the status of the port.
All emails also got to Miles, the maintainer of the port.
Without the slightest sign of anyone claiming he might work on fixing this port.
Greg (one of the uClinux core maintainers) said the only one he knows who can maintain the port is Miles.
If there's not a single person on linux-kernel who is either interested in this port or at least knows someone who is, then requiring to put it into some file in the kernel sources is actually quite high on the scale of pointless bureaucracy.
Quoted 1 line
roland
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed