[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.58.0805060634330.12081@gandalf.stny.rr.com>
Date: Tue, 6 May 2008 06:40:13 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: Daniel Walker <dwalker@...sta.com>
cc: Thomas Gleixner <tglx@...utronix.de>,
Sven-Thorsten Dietrich <sven@...bigcorporation.com>,
Remy Bohmer <linux@...mer.net>,
LKML <linux-kernel@...r.kernel.org>,
RT <linux-rt-users@...r.kernel.org>,
Jon Masters <jonathan@...masters.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: Preempt-RT patch for 2.6.25
On Mon, 5 May 2008, Daniel Walker wrote:
> On Mon, 2008-05-05 at 23:01 +0200, Thomas Gleixner wrote:
> >
> > Keeping the architecture ports even in a maybe disfunctional state in
> > the queue is important as we move them along and make the obvious
> > changes to them so anyone interested to bring them up to date has not
> > to start from scratch again, which is a major PITA (we just did one
> > from scratch)
>
> In open source code never dies. So I'm not sure where this "From
> scratch" stuff is coming from ..
Dropping someones work from the official tree is an insult to the
developer that did that work. The *only* reason to drop code is if it
happens to break something else that already existed or it has been warned
for at least one year that if no one maintains this code it will be
dropped. Dropping it for the sake of making "my work easier" is not an
excuse.
Don't say "well it's only temporary" because it's not. You even expected
the ones that did the work to "re-port" it to your new tree. Sorry Daniel,
that's not the way things happen in Open Source.
>
> I've done ports from scratch and it's not that bad.. Not sure what your
> porting too.. It would also be a lot easier to do an arch port piece by
> piece under a bisectable tree.
Refresh my memory, which ports have you submitted? I don't recall seeing
a port from scratch that was from you.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists