From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>
Subject: Re: kernel oops in cfi_cmdset_0002.c:do_write_one()...
Date: Thu, 8 Apr 2004 21:47:34 +0200 [thread overview]
Message-ID: <20040408194734.GA6743@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200404082128.23060.tglx@linutronix.de>
On Thu, 8 April 2004 21:28:23 +0200, Thomas Gleixner wrote:
> On Thursday 08 April 2004 16:37, Jörn Engel wrote:
> >
> > Don't blame him, this is the result of using CVS, which is designed
> > around the assumption of a single central repository. If current sync
> > speed is to slow for you, try to make it easier for him to send
> > patches forward.
>
> I don't know, if he is really happy, if everybody starts to send patches
> upstream. He does a good job on this and he focussed more on 2.6 in the last
> months. But I'm sure that he can be convinced to bring 2.4 to the same state
> as 2.6 at least. On the other hand we live very well with the MTD patches
> since long, so what :) I never trust the kernel stuff of subsystems, which
> have a active development team :)
That was not what I meant (although it did sound confusing, sorry).
You can prepare patches and send them to David. Preparing those
patches is stupid and boring work, I guess David likes it as little as
I do. Then he can see if they are good enough and send them forward.
Or, alternatively, you can accept the current situation as the best
you can get for your money, which is for free.
Jörn
--
My second remark is that our intellectual powers are rather geared to
master static relations and that our powers to visualize processes
evolving in time are relatively poorly developed.
-- Edsger W. Dijkstra
next prev parent reply other threads:[~2004-04-08 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 15:43 kernel oops in cfi_cmdset_0002.c:do_write_one() Steven Scholz
2004-04-07 16:19 ` Thayne Harbaugh
2004-04-07 16:47 ` David Vrabel
2004-04-11 11:40 ` Steven Scholz
2004-04-08 7:16 ` Steven Scholz
2004-04-08 13:29 ` Steven Scholz
2004-04-08 14:37 ` Jörn Engel
2004-04-08 19:28 ` Thomas Gleixner
2004-04-08 19:47 ` Jörn Engel [this message]
2004-04-09 12:42 ` David Woodhouse
2004-04-13 9:31 ` Jörn Engel
2004-04-13 14:28 ` David Woodhouse
2004-04-13 11:04 ` David Vrabel
[not found] <D73A25AA6E54D511AD74009027B1110F5BB16A@ORION>
2004-04-07 16:12 ` Steven Scholz
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=20040408194734.GA6743@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--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