From: Eugene Surovegin <ebs@ebshome.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: David Woodhouse <dwmw2@infradead.org>,
Song Sam <samlinuxppc@yahoo.com.cn>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.4 versus 2.6 patches
Date: Mon, 26 Jul 2004 16:49:04 -0700 [thread overview]
Message-ID: <20040726234904.GA15924@gate.ebshome.net> (raw)
In-Reply-To: <1090883872.20889.11.camel@thomas.tec.linutronix.de>
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/
next prev parent reply other threads:[~2004-07-26 23:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 14:57 2.4 versus 2.6 patches Robert P. J. Day
2004-07-24 15:20 ` David Woodhouse
2004-07-26 2:50 ` Song Sam
2004-07-26 4:13 ` David Woodhouse
2004-07-26 4:40 ` Eugene Surovegin
2004-07-26 13:48 ` Song Sam
2004-07-26 14:27 ` David Woodhouse
2004-07-26 15:08 ` Mark Chambers
2004-07-26 15:53 ` Robert P. J. Day
2004-07-26 16:30 ` Eugene Surovegin
2004-07-26 23:17 ` Thomas Gleixner
2004-07-26 23:49 ` Eugene Surovegin [this message]
2004-07-27 0:25 ` Thomas Gleixner
2004-07-29 19:30 ` David Woodhouse
2004-07-26 17:16 ` Wolfgang Denk
2004-08-09 15:03 ` Marcelo Tosatti
2004-07-27 3:13 ` Song Sam
2004-08-09 13:28 ` Marcelo Tosatti
2004-08-10 5:58 ` Song Sam
2004-08-10 11:54 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 16:48 Demke, Torsten
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=20040726234904.GA15924@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=dwmw2@infradead.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
--cc=samlinuxppc@yahoo.com.cn \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).