From: Dave Jones <davej@redhat.com>
To: Duncan Sands <baldrick@free.fr>
Cc: dan@eglifamily.dnsalias.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 problems
Date: Mon, 29 Dec 2003 21:46:34 +0000 [thread overview]
Message-ID: <20031229214634.GA18738@redhat.com> (raw)
In-Reply-To: <200312291151.50763.baldrick@free.fr>
On Mon, Dec 29, 2003 at 11:51:50AM +0100, Duncan Sands wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/davej/misc/post-halloween-2.5.txt
s/2.5/2.6/
That was a really old revision, latest just copied there from its
new home at http://www.linux.org.uk/~davej/docs/
Hopefully in the new year I'll have the data off the now dead
codemonkey.org.uk server and all that stuff will go back online..
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2003-12-29 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-25 20:57 2.6.0 problems dan
2003-12-25 22:07 ` Eric
2003-12-26 1:07 ` dan
2003-12-26 1:52 ` Eric
2003-12-26 5:09 ` Joshua Schmidlkofer
2003-12-29 10:51 ` Duncan Sands
2003-12-29 21:46 ` Dave Jones [this message]
2004-01-05 23:37 ` James Simmons
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=20031229214634.GA18738@redhat.com \
--to=davej@redhat.com \
--cc=baldrick@free.fr \
--cc=dan@eglifamily.dnsalias.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