From: Jos Hulzink <josh@stack.nl>
To: Mike Galbraith <efault@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Give Bartlomiej a break! (Re: Impressions of IDE 98?)
Date: Sun, 21 Jul 2002 11:10:40 +0200 (CEST) [thread overview]
Message-ID: <20020721105014.U26890-100000@toad.stack.nl> (raw)
In-Reply-To: <5.1.0.14.2.20020721102202.00b9b3d0@pop.gmx.net>
On Sun, 21 Jul 2002, Mike Galbraith wrote:
> >Well you don't necessarily have to be an IDE guru to realize something's
> >wrong when you see a bloke constantly breaking the subsystem, practically
> >never fixing it up himself, disappearing for a month w/o saying a word
> >after having fried 2.5.25 completely and not really caring about what
> >others have to say about the code.
>
> No, you don't have to be a guru to notice that the rewrite is proving
> difficult.
You are right there, but anyone could have told you that even before the
rewrite started. A rewrite of the IDE drivers should mean one out of two
things:
1) You are aware of the fact IDE disks contain user data, thus if you hack
the ide drivers, you better do / test it thoroughly. Of course, you are
not perfect, mistakes are possible, but know that people won't like them.
2) You assume EVERYONE that is working on the development kernel (even on
parts that have nothing to do with IDE) has a seperate computer for kernel
development or SCSI disks. (You don't want your IDE driver to destroy that
data partition / disk, do you ?).
Well... IMHO, 2) is not an option for a good maintainer, and at the
moment, 1) seems not to hold.
I was willing to test the 2.5 tree, but the way IDE development is going
at the moment makes me keeping my hands off any 2.5 kernel. I just don't
have a second system that is fast enough to recomile a kernel every few
days.
Well... I already gave my opinion about the IDE maintenance in the early
2.5 days, glad to see I was right back then.
Guys, see you again after 2.6.0, I probably won't compile any single
kernel before then.
Jos
next prev parent reply other threads:[~2002-07-21 9:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-20 4:51 Impressions of IDE 98? Thunder from the hill
2002-07-20 5:02 ` Arnaldo Carvalho de Melo
2002-07-20 6:51 ` Skip Ford
2002-07-20 14:26 ` Bartlomiej Zolnierkiewicz
2002-07-20 21:16 ` Thunder from the hill
2002-07-20 21:25 ` Tomas Szepe
2002-07-20 21:32 ` Bartlomiej Zolnierkiewicz
2002-07-20 22:17 ` Tomas Szepe
2002-07-21 5:28 ` Give Bartlomiej a break! (Re: Impressions of IDE 98?) Andre Hedrick
2002-07-21 5:58 ` Tomas Szepe
2002-07-21 6:14 ` Thunder from the hill
[not found] ` <Pine.LNX.4.44.0207210006410.3309-100000@hawkeye.luckynet.a dm>
2002-07-21 7:24 ` Mike Galbraith
2002-07-21 7:31 ` Thunder from the hill
2002-07-22 6:11 ` Vojtech Pavlik
[not found] ` <Pine.LNX.4.44.0207210130020.3309-100000@hawkeye.luckynet.a dm>
2002-07-21 8:13 ` Mike Galbraith
2002-07-21 8:23 ` Tomas Szepe
2002-07-21 8:36 ` Mike Galbraith
2002-07-21 9:10 ` Jos Hulzink [this message]
2002-07-21 9:52 ` Zwane Mwaikambo
2002-07-21 8:26 ` Thunder from the hill
2002-07-20 15:18 ` Impressions of IDE 98? Arkadiusz Miskiewicz
2002-07-20 21:58 ` Bartlomiej Zolnierkiewicz
2002-07-21 23:04 Give Bartlomiej a break! (Re: Impressions of IDE 98?) Bartlomiej Zolnierkiewicz
[not found] <Pine.SOL.4.30.0207220032410.15795-100000@mion.elka.pw.edu. pl>
2002-07-22 4:49 ` Mike Galbraith
2002-07-22 5:05 ` Thunder from the hill
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=20020721105014.U26890-100000@toad.stack.nl \
--to=josh@stack.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®