From: Alan Cox <alan@redhat.com>
To: szepe@pinerecords.com (Tomas Szepe)
Cc: andre@linux-ide.org (Andre Hedrick),
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
alan@redhat.com
Subject: Re: ide-2.4.20-pre4-ac2.patch
Date: Wed, 28 Aug 2002 16:49:55 -0400 (EDT) [thread overview]
Message-ID: <200208282049.g7SKntM06459@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020828204130.GA16551@louise.pinerecords.com> from "Tomas Szepe" at Aug 28, 2002 10:41:30 PM
> In the end it _was_ the new code that made me feel soooo happy
> today. So another sorry goes to Alan for blaming 2.4.20-pre4-ac2.
> What a fine example of hasty reporting I've managed to display. :)
I appreciate all the testing immensely. Now I know to merge just the
obvious bits of that patch piece by piece as I was thinking I ought to.
next prev parent reply other threads:[~2002-08-28 20:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 22:17 ide-2.4.20-pre4-ac2.patch Andre Hedrick
2002-08-28 7:59 ` ide-2.4.20-pre4-ac2.patch Markus Plail
2002-08-28 9:15 ` ide-2.4.20-pre4-ac2.patch Jurriaan
2002-08-28 17:59 ` ide-2.4.20-pre4-ac2.patch Tomas Szepe
2002-08-28 18:20 ` ide-2.4.20-pre4-ac2.patch Andre Hedrick
2002-08-28 18:26 ` ide-2.4.20-pre4-ac2.patch Tomas Szepe
2002-08-28 18:28 ` ide-2.4.20-pre4-ac2.patch Andre Hedrick
2002-08-28 18:31 ` ide-2.4.20-pre4-ac2.patch Tomas Szepe
2002-08-28 20:41 ` ide-2.4.20-pre4-ac2.patch Tomas Szepe
2002-08-28 20:49 ` Alan Cox [this message]
2002-08-29 22:55 ` ide-2.4.20-pre4-ac2.patch Alan Cox
2002-08-29 23:16 ` ide-2.4.20-pre4-ac2.patch Roman Zippel
2002-08-29 23:21 ` ide-2.4.20-pre4-ac2.patch Alan Cox
2002-08-29 23:43 ` ide-2.4.20-pre4-ac2.patch Roman Zippel
2002-08-30 9:43 ` ide-2.4.20-pre4-ac2.patch Benjamin Herrenschmidt
2002-08-30 1:01 ` ide-2.4.20-pre4-ac2.patch Daniel Egger
2002-08-30 7:36 ` ide-2.4.20-pre4-ac2.patch Roman Zippel
2002-08-30 3:36 ` ide-2.4.20-pre4-ac2.patch Andre Hedrick
2002-08-30 9:40 ` ide-2.4.20-pre4-ac2.patch Benjamin Herrenschmidt
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=200208282049.g7SKntM06459@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=andre@linux-ide.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=szepe@pinerecords.com \
/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).