public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Gareth Bult <gareth@linux.co.uk>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Re; MTD (2) Block Driver broken
Date: Mon, 7 Mar 2005 15:24:02 +0100	[thread overview]
Message-ID: <20050307142402.GC9597@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1110200816.11535.15.camel@squizzey.bult.co.uk>

On Mon, 7 March 2005 13:06:56 +0000, Gareth Bult wrote:
> 
> Ahh, right, that makes sense.
> 
> I re-write a driver so it works properly.
> 
> You clean up all the code I've written to the extent that it no longer
> works. (was it 22 different patches?)
> 
> Code gets submitted to kernel (obviously without testing) and ends up in
> the live tree as broken code.
> 
> And it it's "my" fault for not checking and fixing all YOUR changes ?!
> 
> Right.

Sure.  You have your reasons to be pissed and I have no problem to
acknowledge them.  The current driver is broken and a fscking
embarrassment.  And I am to blame.  No doubt.

Yet - you have proven before and continue to prove than you are
impossible to work with:

> Well, firstly I have in interest in the integrity of the kernel tree -
> I've been working with it and on it since 1991. Secondly, you inserted
> my name into your broken code - I do not appreciate this.
> 
> What would I like, I would suggest one of;
> 
> a.    Fix your changes, TEST, and re-submit to the kernel tree
> or
> b.    Remove the new driver from the kernel tree
> 
> Either way, I would appreciate it greatly if you would remove my name
> from your work.

Deal.  Thank you for the original code.  It is a shame, but apparently
working without you is the only possible solution.

> Incidentally, there's nothing wrong with my memory (yet) and I'm still
> not interested in working on the mtd driver for exactly the same reasons
> as previously mentioned.

In that case, I shall consider it a an act of extreme politeness that
you directed your constructive criticism personally to me.  Very
efficient on so many levels.

Jörn, trying his best not to flame

-- 
"Error protection by error detection and correction."
-- from a university class

  reply	other threads:[~2005-03-07 14:24 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 17:26 Re; MTD (2) Block Driver broken Gareth Bult
2005-03-07 11:04 ` Jörn Engel
2005-03-07 11:13   ` Jörn Engel
2005-03-07 12:45     ` Josh Boyer
2005-03-07 12:52       ` Jörn Engel
2005-03-07 13:06   ` Gareth Bult
2005-03-07 14:24     ` Jörn Engel [this message]
2005-03-07 18:34       ` Gareth Bult
2005-03-07 19:00         ` Jörn Engel
     [not found]           ` <1110222770.11437.51.camel@squizzey.bult.co.uk>
2005-03-07 19:15             ` Jörn Engel
2005-03-07 20:42               ` Jörn Engel
2005-03-07 20:21           ` David Woodhouse
2005-03-07 20:57             ` Gareth Bult
2005-03-07 21:07               ` Jörn Engel
2005-03-07 21:46                 ` Gareth Bult
2005-03-07 22:01                   ` Jörn Engel
2005-03-07 22:20                     ` Gareth Bult
2005-03-07 22:42                       ` Jörn Engel
2005-03-08 10:33                         ` Gareth Bult
2005-03-08 10:44                           ` Jörn Engel
2005-03-07 21:26               ` David Woodhouse
2005-03-07 22:10                 ` Gareth Bult
2005-03-07 22:20                   ` David Woodhouse
2005-03-07 22:26                     ` Gareth Bult
2005-03-07 22:30                       ` David Woodhouse
2005-03-08 10:24                         ` Gareth Bult
2005-03-08 11:05                           ` David Woodhouse
2005-03-08 11:27                             ` Gareth Bult
2005-03-07 22:33                   ` Jörn Engel
2005-03-08 10:31                     ` Gareth Bult

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=20050307142402.GC9597@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=gareth@linux.co.uk \
    --cc=linux-mtd@lists.infradead.org \
    /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