From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Dave Jones <davej@suse.de>
Cc: Skip Ford <skip.ford@verizon.net>, <linux-kernel@vger.kernel.org>
Subject: Re: linux 2.5.4-pre3 and IDE changes
Date: Fri, 08 Feb 2002 04:52:23 +0000 [thread overview]
Message-ID: <5.1.0.14.2.20020208045006.00b2e4d0@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0202080508410.29741-100000@Appserv.suse.de>
In-Reply-To: <20020208035851.KOPJ10804.out006.verizon.net@pool-141-150-235-204.delv.east.verizon.net>
At 04:10 08/02/02, Dave Jones wrote:
>On Thu, 7 Feb 2002, Skip Ford wrote:
>
> > This is the patch that Jens posted, though he posted it before this
> > kernel was even released. His post said it fixed a compile error
> > in pre2, but pre2 compiled fine. It _does_ fix the compile error in
> > pre3 though.
>
>As more developers start pulling Linus' bitkeeper tree, you'll probably
>see more bugs getting fixed before they're reported 8-)
Ah, but taking this one step further, most people will never see the bugs
as the fixes will be applied by Linus before he releases the pending pre
kernel so the pre kernel won't have the bug. (-8
Only the bk changelog will tell us they ever existed... (-;
Anton
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2002-02-08 4:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 3:17 John Weber
2002-02-08 3:29 ` flaniganr
2002-02-08 3:47 ` Jeff Garzik
2002-02-08 3:54 ` Andre Hedrick
2002-02-08 6:09 ` Skip Ford
2002-02-08 7:21 ` Vojtech Pavlik
2002-02-08 3:56 ` Skip Ford
2002-02-08 4:10 ` Dave Jones
2002-02-08 4:52 ` Anton Altaparmakov [this message]
[not found] <fa.c2cp66v.1dgedgb@ifi.uio.no>
[not found] ` <fa.10ej114v.oj62bd@ifi.uio.no>
2002-02-08 4:05 ` John Weber
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=5.1.0.14.2.20020208045006.00b2e4d0@pop.cus.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=skip.ford@verizon.net \
/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®