From: devzero@web.de
To: Adrian Bunk <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [2.6 patch] remove the v850 port
Date: Tue, 22 Apr 2008 08:59:26 +0200 [thread overview]
Message-ID: <248793158@web.de> (raw)
sounds reasonable, thanks for explaining.
indeed this is an exceptional case and when there was a timeslot for adding to feature-removal-schedule.txt, then that was 3 months (or even more) ago.
thanks
roland
> -----Ursprüngliche Nachricht-----
> Von: "Adrian Bunk" <bunk@kernel.org>
> Gesendet: 22.04.08 02:01:20
> An: devzero@web.de
> CC: linux-kernel@vger.kernel.org, mingo@elte.hu
> Betreff: Re: [2.6 patch] remove the v850 port
> On Tue, Apr 22, 2008 at 01:38:49AM +0200, devzero@web.de 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.
> >
> > 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 people`s 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.
>
> > roland
>
> cu
> Adrian
>
> --
>
> "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
>
>
_______________________________________________________________
Schon gehört? Der neue WEB.DE MultiMessenger kann`s mit allen:
http://www.produkte.web.de/messenger/?did=3016
next reply other threads:[~2008-04-22 6:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 6:59 devzero [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-05-05 18:28 [2.6 patch] remove the v850 port Adrian Bunk
2008-04-21 23:38 devzero
2008-04-22 0:00 ` Adrian Bunk
2008-04-21 21:33 Adrian Bunk
2008-04-21 23:37 ` Greg Ungerer
2008-04-14 18:14 Adrian Bunk
2008-03-30 22:49 Adrian Bunk
2008-03-03 18:07 Adrian Bunk
2008-02-27 21:20 Adrian Bunk
2008-02-13 21:30 Adrian Bunk
2008-01-20 19:23 RFC: Removal of the v850 port? Adrian Bunk
2008-01-21 0:15 ` Greg Ungerer
2008-01-28 22:13 ` [2.6 patch] remove the v850 port Adrian Bunk
2008-02-01 15:14 ` Ingo Molnar
2008-02-05 11:25 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=248793158@web.de \
--to=devzero@web.de \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.