From: Alan Cox <alan@redhat.com>
To: vherva@niksula.hut.fi (Ville Herva)
Cc: alan@redhat.com (Alan Cox), linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.18pre3-ac1
Date: Sun, 13 Jan 2002 17:57:30 -0500 (EST) [thread overview]
Message-ID: <200201132257.g0DMvU905716@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020113225244.GC51648@niksula.cs.hut.fi> from "Ville Herva" at Jan 14, 2002 12:52:44 AM
> On Sun, Jan 13, 2002 at 04:44:46PM -0500, you [Alan Cox] claimed:
> > People keep bugging me about the -ac tree stuff so this is whats in my
> > current internal diff with the ll patch and the ide changes excluded.
>
> Any big reason why you aren't including those two? I'm pretty sure a lot of
> people will eventual bug Marcelo (and you) about merging ide to 2.4
> proper (or -ac)... :)
So I can tell which patch causes problems if any
> 2.4.10ac10 (which is what I ran before 17rc1) never showed this. I wan't
> able to reproduce it on purpose.
>
> I guess this is not the fix for that?
Thats the first I've heard of the other problem
next prev parent reply other threads:[~2002-01-13 22:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 21:44 Linux 2.4.18pre3-ac1 Alan Cox
2002-01-13 19:23 ` Thiago Rondon
2002-01-13 22:52 ` Ville Herva
2002-01-13 22:57 ` Alan Cox [this message]
2002-01-14 0:15 ` Adam Kropelin
2002-01-14 0:47 ` Alan Cox
2002-01-14 2:13 ` Benjamin LaHaise
2002-01-14 2:54 ` Rik van Riel
2002-01-14 5:47 ` Eric W. Biederman
2002-01-14 6:17 ` Rik van Riel
2002-01-14 7:25 ` Eric W. Biederman
2002-01-14 9:28 ` David S. Miller
2002-01-14 12:05 ` Rik van Riel
2002-01-21 3:46 ` Daniel Phillips
2002-01-21 5:30 ` Richard Gooch
2002-01-21 5:34 ` Rik van Riel
2002-01-21 7:01 ` Eric W. Biederman
2002-01-21 12:02 ` Rik van Riel
2002-01-21 14:02 ` Daniel Phillips
2002-01-21 13:22 ` Daniel Phillips
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=200201132257.g0DMvU905716@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@niksula.hut.fi \
/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