Date: Sun, 2 Jan 2005 22:01:51 +0100
From: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Reply-To: Maciej Soltysiak <solt2@dns.toxicfilms.tv>
Message-ID: <1833976182.20050102220151@dns.toxicfilms.tv>
To: linux-kernel@vger.kernel.org
Subject: Re[2]: starting with 2.7
In-Reply-To: <20050102203615.GL29332@holomorphy.com>
References: <1697129508.20050102210332@dns.toxicfilms.tv>
 <20050102203615.GL29332@holomorphy.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1254
Lines: 32

Hello William,

Sunday, January 2, 2005, 9:36:15 PM, you wrote:
> I have a plan to never ever stop experimental code, which is to
> actually move on the 2.6.x.y strategy if no one else does and these
> kinds of complaints remain persistent and become more widespread.
Well, personally I like the 2.6.x.y idea.

> There is a standard. Breaking things and hoping someone cleans up
> later doesn't work. So it has to be stable all the time anyway, and
> this is one of the observations upon which the "2.6 forever" theme is
> based.
Hm, now that I think about it, it has an advantage. eg. No problems
for other people with maintaining code for 2.4, 2.5, 2.6, ...

Anyway, starting with other trees like 2.7 sends a signal to people, that
something huge is going to happen. Like totally new ideas that require
to change the APIs, rewrite all the drivers (I know nobody likes that, really)
etc...

I was asking If something like this is about to happen.
Is a stockpile of things like this building up?

--
Maciej


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/