2.4 versus 2.6 patches

[Eugene Surovegin]

On Tue, Jul 27, 2004 at 01:17:52AM +0200, Thomas Gleixner wrote:
> > Hopefully, I can maintain this stuff myself and backport fixes (what I already
> > did for some MTD stuff, btw).
>
> Cool (where are the patches, btw ???).

All stuff I backported into my 2.4.21 tree _are_ from MTD CVS (e.g. write buffer
support for AMD flashes). When I found bugs in MTD layer, I submit patches
through usual channels.

> We would certainly be happy to keep a 2.4 branch of MTD alive if there
> would be any noticable support available instead of whinging about the
> brokenness of the MTD CVS.

Could you point to any e-mail where I was whining about brokenness of MTD CVS?
If not, what was the purpose of your statement?

This is the exact attitude which will not help you to get "any noticeable
support".

> But we certainly do not get any further, when people have patches around
> and complain why we have not included them into MTD CVS by magic
> awareness of the solution.

What is your point? Do you accuse me of not contributing back patches? I always
do this.

You missed the point of this discussion. We wasn't talking about some
random patches floating around. We were talking about stuff which _is_ in 2.6
but not 2.4. Also, we were talking about how mature is 2.6 for production
environment and how "dead" is 2.4

Of course, it's up to maintainer to decide what to backport or not, _nobody_
here asks you or David or anybody else to backport anything.

This is what I _love_ about OSS - I don't depend on any vendor/person/whoever.

Eugene.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/