From: Josh McKinney <forming@charter.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.5.64-mm8
Date: Sun, 16 Mar 2003 14:20:36 -0500 [thread overview]
Message-ID: <20030316192036.GA30075@cy599856-a> (raw)
In-Reply-To: <20030316024239.484f8bda.akpm@digeo.com>
On approximately Sun, Mar 16, 2003 at 02:42:39AM -0800, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.64/2.5.64-mm8/
>
Maybe I am just slow but it seems that -mm8 didn't make it to kernel.org from
where I am sitting.
--
Josh McKinney | Webmaster: http://joshandangie.org
--------------------------------------------------------------------------
Linux, the choice | Mate, this parrot wouldn't VOOM if you put
of a GNU generation -o) | four million volts through it! -- Monty
Kernel 2.5.64-mm6 /\ | Python
on a Athlon-XP _\_v |
|
next prev parent reply other threads:[~2003-03-16 19:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 10:42 2.5.64-mm8 Andrew Morton
2003-03-16 11:45 ` [patch] 2.5.64-mm8: fs/affs/dir.c doesn't compile Adrian Bunk
2003-03-16 12:21 ` 2.5.64-mm8 Roman Zippel
2003-03-16 13:02 ` 2.5.64-mm8: drivers/atm/idt77252.c doesn't compile Adrian Bunk
2003-03-16 15:44 ` Adrian Bunk
2003-03-17 15:43 ` [Linux-ATM-General] " chas williams
2003-03-18 20:49 ` Adrian Bunk
2003-03-20 8:44 ` David S. Miller
2003-03-16 18:00 ` Adrian Bunk
2003-03-16 13:43 ` [patch] 2.5.64-mm8: miropcm20-rds.c " Adrian Bunk
2003-03-16 13:49 ` 2.5.64-mm8 Mike Galbraith
2003-03-16 17:12 ` 2.5.64-mm8 Helge Hafting
2003-03-16 19:10 ` 2.5.64-mm8: link error with CONFIG_NUMA and !CONFIG_SMP Adrian Bunk
2003-03-16 19:32 ` Martin J. Bligh
2003-03-16 19:44 ` Martin J. Bligh
2003-03-16 19:58 ` Adrian Bunk
2003-03-16 19:20 ` Josh McKinney [this message]
2003-03-16 16:18 2.5.64-mm8 Shane Shrybman
2003-03-17 23:19 2.5.64-mm8 rwhron
2003-03-17 23:26 ` 2.5.64-mm8 Robert Love
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=20030316192036.GA30075@cy599856-a \
--to=forming@charter.net \
--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®