From: jbradford@dial.pipex.com
To: linux-kernel@vger.kernel.org
Subject: patch-2.5.40 mirror
Date: Tue, 1 Oct 2002 17:11:09 +0100 [thread overview]
Message-ID: <200210011611.g91GB9rV002445@darkstar.example.net> (raw)
Just in case SF goes down, (yeah, I know, not likely, but you never know), I've put the following on-line:
http://www.jbradford.dial.pipex.com/patch-2.5.40.bz2
http://www.jbradford.dial.pipex.com/patch-2.5.40.gz
so, there is no excuse not to test the 2.5.40 kernel ;-), who cares if it hoses your IDE drive or not, (not that it will, (probably)).
John.
reply other threads:[~2002-10-01 15:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200210011611.g91GB9rV002445@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--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;
as well as URLs for NNTP newsgroup(s).